Repository navigation
Fix range parsing with dotted lookup keys - #2138
Open
efegokdemir wants to merge 2 commits into
Open
efegokdemir wants to merge 2 commits into
efegokdemir wants to merge 2 commits into
Conversation
This branch has not been deployed
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.
Range parsing can mistake
..inside a quoted lookup key for its separator, producing incorrect loop values for endpoints such aspaths[".."]andpaths["..."]. This keeps the existing fast path for ordinary ranges and scans for the separator outside quoted and bracketed lookups when the regex match is incomplete. Regression coverage exercises dotted lower and upper bounds.The default
bundle exec raketasks passed on Ruby 4.0.7 using a task-local Gemfile that omits the spec-only Git dependency. RuboCop inspected 160 files with no offenses. Related to #1890.