Make DidYouMean
integration optional
#86
Merged
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.
The gem won't load when DidYouMean is disabled with
--disable-did_you_mean:
With this commit, the gem loads even though some tests fail.
We run some of our Ruby apps with
--disable-did_you_mean
for performance reasons, hence the change.I didn't write any tests for this. The only test I could think of would be something like shelling out to load a new Ruby interpreter without
DidYouMean
and validating that it doesn't fail:I didn't see a lot of value in such test, but open to feedback or alternative.