Cover corner-cases when updating option names - #3446
Merged
Conversation
ZedThree
requested changes
Aug 3, 2026
ZedThree
left a comment
ZedThree
left a comment
Member
There was a problem hiding this comment.
One small clarification that I think helps (not tested)
Co-authored-by: Peter Hill <peter.hill@york.ac.uk>
ZedThree
approved these changes
Aug 5, 2026
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
2 participants
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.
Following #3445, I realised that there were some corner cases in updating option names that I hadn't accounted for. This is related to when one or both of the operands have no name. In that case the path wasn't always updated correctly. This PR adds additional checks and logic to ensure everything works as it should.