Explain metadata registry requirement for PATCH paths #312
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.
Currently, metadata PATCH requests with
"op": "replace"and an unknown metadata field in thepathare treated as if they have"path": "/metadata". This can lead to unexpected loss of metadata as detailed in DSpace/DSpace#10817This PR documents the changes made in DSpace/DSpace#10961 to resolve this problem: any unknown field in the
pathwill immediately lead to an HTTP 422 response.The change affects all PATCH operations, to avoid similar problems.