Allows command arguments to consist of only 'escaped' characters

[Quahu]

Say, we have a command that looks like this:

[Command("test")]
public Task TestAsync(string parameter)
    => ReplyAsync(parameter);

Our prefix will be an exclamation mark.
Invoking it as !test :x: will work perfectly fine, but invoking it as !test \:x: will fail, returning a ParseResult with the error message: The input text has too few parameters..
Also, invoking commands this way with params T[] parameters will invoke the actual command, but with an empty array.

I tested it after my changes, and it seemed to work as expected.

I hope I don't break the lib with this.

[Joe4evr]

How is this different from using [Remainder]?

[AntiTcb]

Well, you could have parameters after it for one thing.

[Quahu]

@Joe4evr RemainderAttribute wouldn't prevent it from breaking. It would still return the ParseResult in the case I mentioned.

[FiniteReality]

Is there any reason why we couldn't move the remainder param logic above the escape logic rather than move the escape logic to after handling the default state for the parser?

[Quahu]

Erm, if I understood your question correctly - it wouldn't fix the characters being escaped. It's not an issue with remainder parameters, but normal parameters.

[foxbot]

lgtm