Open nexy7574 opened 6 days ago
This is now fixed in fix/argument-parsing
, but be warned, there has not been extensive testing. There are possible regressions relating to optional arguments, positional arguments, argument typing, and even argument parsing. If anyone tests this out, please let me know how it worked out for you ("works for me" is just as valuable as "it didnt work for me")
Describe the bug When providing a
*, keyword
argument in a command function definition, the library is supposed to make it a "greedy" argument, in that any content unconsumed goes into that variable. Right now, this does not happen.To Reproduce Run this simple example:
Expected behavior
!echo foo bar
should respond withfoo bar
, however, the too many arguments exception is raisedAdditional context Using "quotes" gets around this issue, so the issue may simply just be the command parser being too strict when counting arguments and prematurely raising an error.