Daniel Duan

Doesn't support CLI arguments file

1

Certain OSes limit the number of CLI arguments for any command. Usual solution is a file that contains all the command options.

A common-ish mistake for docstring author is to use the label of a parameter as opposed to the actual name. The error message in this scenario could be improved. Right...

`//` in continuation lines aren't reported as problems

1

``` /// blah blah blah //

No way to concatenate continuous lines

2

When an docstring entry spans multiple lines, there's no option to join them in addition to breaking over-the-column-limit lines up to newlines. Sometimes user may prefer automatic joining behavior. For...

`- note:` is not recognized?

1

This is a common-ish element. Should consider whether to check whitespace errors when it exists.

When parameter docs are out of order, the report is confusing

1

Right now you'll get a problem for a missing doc, and a problem for a redundant doc. There might be a good algorithm out there that could infer this better.

In recent release, we added the ability to use command line argument to override config file options. If this was done for excluded files, and the exclusion is superfluous, the...

sometimes it's desirable to enforce it. (question mark, exclamation point, etc)

```swift /// docstring starts 1 space off func foo() ``` this should be problematic.