You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version 13.0.0 of commander introduced a breaking change on excess of command-arguments. #793
Our CI was failing with error: too many arguments. Expected 0 arguments but got 1 in parseRestoreArgs, but a reason for that is not clear. For now I just set allowExcessArguments() on the parser to revert to the former behaviour, but if possible it would be proper to find out the root cause for the failure and properly fix it, probably by listing expected arguments on parser call.
The text was updated successfully, but these errors were encountered:
The version 13.0.0 of
commander
introduced a breaking change on excess of command-arguments. #793Our CI was failing with
error: too many arguments. Expected 0 arguments but got 1
inparseRestoreArgs
, but a reason for that is not clear. For now I just setallowExcessArguments()
on the parser to revert to the former behaviour, but if possible it would be proper to find out the root cause for the failure and properly fix it, probably by listing expected arguments on parser call.The text was updated successfully, but these errors were encountered: