Allow extra fields in Patcher classes that don't exist in original #98
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.
There was a specific check put in to guard against this behavior, but no tests ensuring this was the behavior - so thought maybe it could be changed.
Example scenario: we have an api, and want to update a user. The user can specify any of the user fields to update. I'd like to use most of the fields to patch the user, but there's some that need massaging first.
In this simple case, I want to use the
UserUpdate
class to patch theUser
class, even though I have to handle the verification/conversion/patching ofroleNames
intoroleIds
myself.It may be that this should be handled through some flag or some enhanced patch api with transformers or something, just wanted to start the discussion.