-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dont mangle key typos. #104
Comments
That's only done if there's a single |
do all nix tools randomly reorder the input in the error message? |
This issue isn't about the fact that there is an error message. this issue is about the formatting and content of the error message. |
It looks like most tools bail on the first unknown option:
I'm not sure if that's better as it gives you less information. |
Carthage/Carthage#1926
I think for the sake of better error messages Commandant should not try and convert flags to a set
Commandant/Sources/Commandant/ArgumentParser.swift
Line 75 in 903eaec
It will mangle a
--key
typo and produce confusing errors.If flags are passed as used ex:
Should become
The text was updated successfully, but these errors were encountered: