[#539] Use non-destructive gsub, fix test stubbing - #540
Merged
Conversation
Owner
Agreed. I wasn't the maintainer when most of the parsing stuff went in (took some time away) and just haven't had the energy to clean things up. Thanks! |
Contributor
|
I guess this is the fix for this issue? EDIT: Yes, it is. Thanks for fixing it! Was just about to report it. |
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.
Closes #539
Apparently I like breaking stuff with my changes 😭 . This PR fixes
gsub!from breaking on frozen string literals.Some of the tests around this were actually stubbing the
bodycall directly, instead of setting the data. I've changed these tests to inject the data instead. As a high-level note, a lot of tests forParserare stubbing private methods, which I don't think is a good way to structure tests.We should be able to test all use cases of
Parserthrough the external API. When we stub, or test directly, internal methods, any implementation change can break any number of other tests, even if the change doesn't affect external behavior.