Skip to content
This repository was archived by the owner on May 29, 2026. It is now read-only.

docs(status-engine): per-schema lifecycle migration plan (closes #408)#414

Closed
rubenvdlinde wants to merge 0 commit into
developmentfrom
feature/migrate-status-engine-to-or-lifecycle
Closed

docs(status-engine): per-schema lifecycle migration plan (closes #408)#414
rubenvdlinde wants to merge 0 commit into
developmentfrom
feature/migrate-status-engine-to-or-lifecycle

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Adoption-only. No central state-machine service exists to migrate — state lives as scattered STATUS_* constants. Per ADR-031, each stateful schema (voorstel, bezwaar, parafeerroute, hoorzitting) gets its own follow-up PR moving its state machine to x-openregister-lifecycle. Closes #408.

@rubenvdlinde rubenvdlinde requested a review from Rem-Dam as a code owner May 11, 2026 21:58
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 8900e86

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
composer ✅ 100/100
npm ✅ 419/419
PHPUnit ⏭️
Newman ⏭️
Playwright

Spec coverage: 5% (21 tests / 456 specs)


Quality workflow — 2026-05-11 22:03 UTC

Download the full PDF report from the workflow artifacts.

@WilcoLouwerse WilcoLouwerse left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Concerns

  • 🟡 Controllers said to call ObjectService::saveObject() directly post-migration, contradicting the stated migration goal
  • 🟡 hoorzitting schema listed in scope note but not covered in tasks or spec

🟢 Minor

  • 🟢 Proposal scope says 'zaak (AWB bezwaar lifecycle)' but no zaak schema is addressed

@rubenvdlinde

Copy link
Copy Markdown
Contributor Author

Auto-closed in error by a force-push bug in the quality-cleanup harness. Reopened as #493 with the same branch and content.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants