Prevent modification of attribute defaults #175
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.
Description
Either freeze the default attribute values (in the case of
Stringor emptyHash/Array) or call aProcto return a unique instance of a mutable object (mostly relevant for theprincipalsattribute ofPermissionTarget). Add a check in theattributemethod to enforce this.Receiving a
FrozenErrorin this case may be unexpected for users, but it will force them into the preferred method of setting attributes (i.e. using the#{name}=setter).Related Issue
Fixes issue #174.
Types of changes
#{name}=setters and relies on this undocumented behavior.)Checklist:
Gemfile.lockhas changed, I have used--conservativeto do it and included the full output in the Description above. (No changes toGemfile.lock)