You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello all, a quick sanity check regarding my expectations of how PATCH should work in the Objects API. My understanding is that I should be able to supply a partial record when using PATCH, that this partial should subsequently be merged with the existing object, and that new merged object should be validated according to the object type's JSON schema. Put differently: the object in the body of a PATCH should not itself have to be valid according to the JSON schema.
@joeribekker Practically speaking, for OIP, not at all -- this was important for the VNG hackathon, but we used a workaround and currently there are no (active) plans to integrate that work into the mainline, so don't raise its priority on our account.
Product versie / Product version
2.4.3
Omschrijf het probleem / Describe the bug
From @swrichards
Hello all, a quick sanity check regarding my expectations of how PATCH should work in the Objects API. My understanding is that I should be able to supply a partial record when using PATCH, that this partial should subsequently be merged with the existing object, and that new merged object should be validated according to the object type's JSON schema. Put differently: the object in the body of a PATCH should not itself have to be valid according to the JSON schema.
TLDR: the test I've written here should pass in my view, but instead I get a 400 with:
Is my understanding of the expected behavior correct?
Stappen om te reproduceren / Steps to reproduce
No response
Verwacht gedrag / Expected behavior
No response
The text was updated successfully, but these errors were encountered: