Enforce immutable mutability checks at runtime in PATCH operations#137
Merged
Enforce immutable mutability checks at runtime in PATCH operations#137
Conversation
Move immutable field validation from parse-time to runtime in patch(), where the resource instance is available. This aligns with RFC 7644 §3.5.2 which allows adding a value to an immutable attribute only if it had no previous value, and tolerates no-op operations (remove on unset fields, replace with identical value).
f9aa332 to
af3be1b
Compare
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.
Move immutable field validation from parse-time to runtime in patch(), where the resource instance is available. This aligns with RFC 7644 §3.5.2 which allows adding a value to an immutable attribute only if it had no previous value, and tolerates no-op operations (remove on unset fields, replace with identical value).