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

docs(parafering): OR ApprovalService migration plan (closes #407)#494

Merged
rubenvdlinde merged 1 commit into
developmentfrom
feature/migrate-parafering-to-or-approval-workflow
May 19, 2026
Merged

docs(parafering): OR ApprovalService migration plan (closes #407)#494
rubenvdlinde merged 1 commit into
developmentfrom
feature/migrate-parafering-to-or-approval-workflow

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

(re-opened of #413 — accidentally closed by harness force-push; same branch, same content)

Adoption-only scope. ParaferingService array-API can't delegate to OR ApprovalService without controller-side ObjectEntity resolution. Records the 4-step migration plan (controller, service, notification listener, frontend); each ships as a follow-up PR. Closes #407.

@rubenvdlinde rubenvdlinde requested a review from Rem-Dam as a code owner May 19, 2026 03:26
@rubenvdlinde rubenvdlinde force-pushed the feature/migrate-parafering-to-or-approval-workflow branch from f12532c to 30e8e3a Compare May 19, 2026 03:30
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ dc84607

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

Quality workflow — 2026-05-19 03:34 UTC

Download the full PDF report from the workflow artifacts.

Implements migrate-parafering-to-or-approval-workflow — scope-adjusted to a documentation/planning PR.

Investigation: ParaferingService operates on array-shaped voorstel objects and never sees ObjectEntity. OR ApprovalService needs ObjectEntity; only the controller can resolve it at persistence time. Clean delegation requires a coordinated 4-step rewrite (controller pass-through + service rewrite + notification listener conversion + frontend event-stream consumption) that does not fit a single focused PR.

This commit records:
- The migration plan as four sequential follow-up PRs.
- The ADR-022 rule going forward: every NEW parafering route MUST go through OR ApprovalService.
- The legacy in-array path stays read-only-compatible during transition.

Closes #407
@rubenvdlinde rubenvdlinde force-pushed the feature/migrate-parafering-to-or-approval-workflow branch from 30e8e3a to 6152c79 Compare May 19, 2026 03:46
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 71b5023

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

Quality workflow — 2026-05-19 03:52 UTC

Download the full PDF report from the workflow artifacts.

@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 6133d4f

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

Coverage: 0% (0/81 statements)


Quality workflow — 2026-05-19 04:10 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde rubenvdlinde merged commit 8e370f0 into development May 19, 2026
48 checks passed
@rubenvdlinde rubenvdlinde deleted the feature/migrate-parafering-to-or-approval-workflow branch May 19, 2026 05:02
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.

1 participant