-
Notifications
You must be signed in to change notification settings - Fork 23
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
Error handling #33
Labels
Comments
We're currently taking advantage of the public modifier in the handlers for the unit tests, as well as the the ExecuteCommand builder action. |
This is ongoing |
joaoopereira
added a commit
to joaoopereira/cli
that referenced
this issue
Jan 3, 2023
replace all log error with throw CliException
joaoopereira
added a commit
to joaoopereira/cli
that referenced
this issue
Jan 3, 2023
replace all log error with throw CliException
joaoopereira
added a commit
to joaoopereira/cli
that referenced
this issue
Jan 3, 2023
replace all log error with throw CliException
joaoopereira
added a commit
to joaoopereira/cli
that referenced
this issue
Jan 4, 2023
replace all log error with throw CliException
m-s-
pushed a commit
that referenced
this issue
Jan 4, 2023
replace all log error with throw CliException
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, for all commands the only way of exiting with a non-zero exit code is by throwing an exception, which polutes the logs quite a bit. In
dotnet/command-line-api
, it should be possible for the handler to provide the exit code, but our handlers return void. This should possibly be refactored.Also, there is no reason for our handlers to be public, though this has been a convention since the beginning.
The text was updated successfully, but these errors were encountered: