Skip to content

backport(778): Command not found message should be configurable #793

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.

Sign up for GitHub

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

Jump to bottom
Closed
github-actions bot opened this issue Jun 20, 2023 · 0 comments
Closed

backport(778): Command not found message should be configurable #793

github-actions bot opened this issue Jun 20, 2023 · 0 comments
Labels
branch/3.1.x Issue for a branch type/backport Is a issue to track backport, use with branch/xxx
Milestone
3.1.2

Comments

@github-actions
Copy link
Contributor

Backport #778
@github-actions github-actions bot added branch/3.1.x Issue for a branch type/backport Is a issue to track backport, use with branch/xxx labels Jun 20, 2023
@jvalkeal jvalkeal added this to the 3.1.2 milestone Jun 20, 2023
jvalkeal added a commit that referenced this issue Jun 20, 2023
@jvalkeal
Make command not found configurable
d159245 
- New CommandNotFoundResultHandler which handles
  CommandNotFound to be able to customize error shown.
- New CommandNotFoundMessageProvider which is a plain
  function given a "context" and returns a string.
  Context contains common info to provide better
  error messages.
- Default provider gives same message but
  removes long stacktrace(which previously originated
  from a common ThrowableResultHandler.
- Backport #778
- Relates #793
jvalkeal added a commit that referenced this issue Jun 23, 2023
@jvalkeal
Document CommandNotFoundMessageProvider
4376b1d 
- Relates #793
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
branch/3.1.x Issue for a branch type/backport Is a issue to track backport, use with branch/xxx
Projects
None yet
Milestone
3.1.2
Development

No branches or pull requests
1 participant
@jvalkeal