Give command misspelled suggestions via did_you_mean gem
#3904
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Suggests alternatives using the did_you_mean gem for CLI commands when they are misspelled.
…to kddeisz-did-you-mean
hsbt
force-pushed
the
kddeisz-did-you-mean
branch
2 times, most recently
from
9949703
to
163c342
Compare
hsbt
force-pushed
the
kddeisz-did-you-mean
branch
from
163c342
to
290db02
Compare
deivid-rodriguez
changed the title
deivid-rodriguez
changed the title
did_you_mean gem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
#2840 is older from the repository merge of bundler. So, It's hard to rebase by the contributor.
What is your fix for the problem, implemented in this PR?
I rebased it with the current master branch. I will merge this PR after passing the all of CI jobs.
Tasks:
I will abide by the code of conduct.