Issue#1491: New rules to handle whitespace around range keywords#1494
Merged
JHertz5 merged 10 commits intojeremiah-c-leary:masterfrom Sep 11, 2025
Merged
Issue#1491: New rules to handle whitespace around range keywords#1494JHertz5 merged 10 commits intojeremiah-c-leary:masterfrom
JHertz5 merged 10 commits intojeremiah-c-leary:masterfrom
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
1 participant
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.
Resolves #1491.
I had to make some minor parser changes to get it to parse range keywords in constrained_array_definitions correctly. The way I did it may be a bit of a hack, I'm open to feedback. The unit tests saved me from introducing a bug that misidentifies
'rangeattributes asrangekeywords - I'm once again very grateful for the quality of the unit testing!