Objects API: ensure mandatory fields aren't required for a HTTP PATCH call

[alextreme]

Thema / Theme

Objecten API

Omschrijving / Description

Taiga Utrecht 325

Mandatory fields in the 'data' of an object are required when sending a HTTP PATCH request, even though that data isn't changed.

Taiga issue has a clear example based on https://github.com/open-objecten/objecttypes/blob/main/community-concepts/Medewerker/medewerker-schema.json which shows that the following fields needs to be sent in when doing a PATCH.

I'm not sure if this classifies as a bug or not, the PATCH RFC leaves this rather open in my eyes but I do agree that it's not how I would expect PATCH to behave

Toegevoegde waarde / Added value

No response

Aanvullende opmerkingen / Additional context

No response

[alextreme]

Anna mentioned that this may have been fixed recently after a comment from Sidney

[danielmursa-dev]

@alextreme, checked, this problem seems already solved in this PR #469
In specific this test passes

objects-api/src/objects/tests/v2/test_object_api.py

Line 336 in ab75c7d

def test_patch_validates_merged_object_rather_than_partial_object(self, m):

where it make a PATCH request with a field that is not required