Skip to content
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

Invalid option->default() does not prettify exceptions #56

Open
emanb29 opened this issue Dec 9, 2015 · 1 comment
Open

Invalid option->default() does not prettify exceptions #56

emanb29 opened this issue Dec 9, 2015 · 1 comment

Comments

@emanb29
Copy link

emanb29 commented Dec 9, 2015

When a value passed to default() does not pass a must() closure, the output should be formatted in the standard prettyprint. However, the current behavior is to throw an ugly exception and stacktrace.

@NeoVance
Copy link
Contributor

The user creating the command should validate the value being supplied to default is an acceptable default. While this type of error could be caught, it should be left up to the user to handle this type of error, since this is not caused by end user input but a mistake made by the programmer using the library.

-1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants