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
It seems that soortPartij is a required field when making a PATCH request on a Partij:
If the field is provided, but set to a value that differs from the current value, the existing partijIdentificatie appears to be set to None (thus leading to an invalid object).
Stappen om te reproduceren / Steps to reproduce
Patching while specifying soortPartij equal to current value works as expected
soortPartij should not be required to PATCH an object. I should (for instance, as in the example above) be able to PATCH the nummer attribute without specifying the soortPartij.
if soortPartijis provided in a PATCH request and is set to a different value than the current soortPartij, it should also require the corresponding partijIdentificatie object for that partij soort. I suspect this lack of validation is a problem elsewhere too (e.g. in the admin panel, see Creating Partij in Admin Interface results in a 500 error #303 ). Setting partijIdentificatie to null violates the API spec, which requires this field.
The text was updated successfully, but these errors were encountered:
Product versie / Product version
Docker image: sha256:1f4307b50728f88d1d8db45b8b692e2f25ecc2e6589a7cb02ec550f8e6981da0 (working tree leading up to 2.6.0)
Omschrijf het probleem / Describe the bug
It seems that
soortPartij
is a required field when making aPATCH
request on aPartij
:If the field is provided, but set to a value that differs from the current value, the existing
partijIdentificatie
appears to be set toNone
(thus leading to an invalid object).Stappen om te reproduceren / Steps to reproduce
Patching while specifying
soortPartij
equal to current value works as expectedPatching without specifying
soortPartij
yields a Bad Request errorPatching with a different
soortPartij
withoutpartijIdentificatie
setspartijIdentificatie
tonull
Verwacht gedrag / Expected behavior
I would expect the behavior to be:
soortPartij
should not be required toPATCH
an object. I should (for instance, as in the example above) be able toPATCH
thenummer
attribute without specifying thesoortPartij
.soortPartij
is provided in aPATCH
request and is set to a different value than the currentsoortPartij
, it should also require the correspondingpartijIdentificatie
object for that partij soort. I suspect this lack of validation is a problem elsewhere too (e.g. in the admin panel, see Creating Partij in Admin Interface results in a 500 error #303 ). SettingpartijIdentificatie
tonull
violates the API spec, which requires this field.The text was updated successfully, but these errors were encountered: