Avoid mutating caller relying-party options - #509
Merged
santiagorodriguez96 merged 1 commit intoSep 3, 2026
Conversation
santiagorodriguez96
approved these changes
Sep 3, 2026
santiagorodriguez96
left a comment
santiagorodriguez96
left a comment
Contributor
There was a problem hiding this comment.
Thanks for this!
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.
CreationOptions currently fills name and id in the caller-owned rp hash. Duplicate it before applying defaults so option construction has no external side effect. Verified with the full 502-example suite, a focused mutation model, RuboCop, and syntax checks on Ruby 4.0 and Ruby 3.2.11.