eho/register-referentie
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity
129 Commits 76 Branches 1 Tag
9089bd5e884d56cdf8f1d8c2a2e57217671f8ebe
Commit Graph
4 Commits
Author SHA1 Message Date
notandClaude Opus 4.8 9089bd5e88 fix(acl): set a resultaat before the eindstatus so OpenZaak accepts the status (refs #75)
CI / lint (pull_request) Successful in 1m29s
Details
CI / build (pull_request) Successful in 1m22s
Details
CI / unit (pull_request) Successful in 1m38s
Details
CI / frontend (pull_request) Successful in 3m2s
Details
CI / mutation (pull_request) Successful in 6m36s
Details
CI / verify-stack (pull_request) Successful in 7m59s
Details 
The status-set integration test hit 400 "resultaat-does-not-exist: Zaak has no
resultaat" — OpenZaak refuses a zaak's eindstatus until the zaak has a resultaat.
Resolve the zaaktype's resultaattype and POST /resultaten before POST /statussen.
Also surface the ZGW response body in the failure exception (EnsureSuccessStatusCode
hid the 400 detail that pinpointed this). Reworked the gateway with shared
GetCatalogusAsync/PostAsync helpers and rewrote the stub-handler tests for the new
4-call flow incl. failure paths. Verified against real OpenZaak (integration test
green) and locally: acl mutation 100%.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-07-14 10:39:19 +02:00
notandClaude Opus 4.8 b697b0d865 feat(acl): set a zaak to its eindstatus via ZGW + POST /statussen endpoint (refs #75) 
The gateway resolves the zaaktype's eindstatus from the catalogus (isEindstatus,
falling back to the highest volgnummer) and POSTs a status against the zaak. Exposed
as POST /statussen for the domain's approve use case. Adds an integration test that
sets the eindstatus against a real OpenZaak and verifies the zaak's current status.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-07-13 16:54:39 +02:00
notandClaude Opus 4.8 4322c607cb fix(acl): buffer the zaak POST body so OpenZaak accepts it (refs #46) 
OpenZaak runs behind uwsgi, which rejects a chunked request body with 400.
JsonContent streams without a Content-Length (Transfer-Encoding: chunked), so
buffer it first. Only a real OpenZaak surfaces this — the integration test from
the previous commit now passes. A unit test asserts a Content-Length is sent
(captured before the stub reads/buffers the body), guarding the fix in the fast
lane and killing the Stryker mutant that would otherwise survive.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-06-29 11:43:27 +02:00
eho 4b2af5c635 feat(acl): ACL skeleton — OpenZaak default-fill (refs #5) (#45)
CI / lint (push) Has been cancelled
Details
CI / build (push) Has been cancelled
Details
CI / unit (push) Has been cancelled
Details
CI / compose-smoke (push) Has been cancelled
Details
2026-06-04 07:50:45 +00:00