Fix up did_you_mean usage #97
Merged
Conversation
This file contains hidden or 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
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.
did_you_mean now checks
Exception.method_defined?(:detailed_message)to determine which method to override per ruby/did_you_mean@62799d7. This breaks our tests because previously we were checkingerror.messageto assert that the error had been corrected, but now we need to checkerror.detailed_message. We need to switch here in the same way they do to support older versions of did_you_mean as well.This PR also handles the case where
--disable-did_you_meanwas supplied on the command line by checking if theDidYouMeanconstant is defined.