Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: zaakobjecttype to resultaattype.py and statustype.py as read… #186

Merged
merged 1 commit into from
Sep 25, 2023

Conversation

MatthijsBekendam
Copy link
Contributor

@MatthijsBekendam MatthijsBekendam commented Sep 21, 2023

…_only. Inside zaakobjecttype, resultaattype and statustype POSTable, not required.

…_only. Inside zaakobjecttype resultaattype and statustype postable, not required.
@MatthijsBekendam MatthijsBekendam merged commit ac917f5 into develop Sep 25, 2023
7 checks passed
@MatthijsBekendam MatthijsBekendam deleted the issue/#2334_zaakobjecttype branch September 25, 2023 07:55
MatthijsBekendam added a commit that referenced this pull request Sep 25, 2023
* feature: zaakobjecttype to resultaattype.py and statustype.py as read_only. Inside zaakobjecttype resultaattype and statustype postable, not required. (#186)

* Catalogi referentie implementatie geeft tekstueel aan geforceerd-bijwerken ipv geforceerd-schrijven #2302 (#185)

* bump : version to 1.3.1 (#187)
@joeribekker
Copy link
Contributor

@MatthijsBekendam it seems like this was implemented in the reverse way. I will detail this in the related ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants