-
Notifications
You must be signed in to change notification settings - Fork 0
fix(procest): repair OR-API drift + dangling seed references #417
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
base: development
Are you sure you want to change the base?
Changes from all commits
ff3d370
a9fe6e5
fa646c1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [CONCERN] Incomplete OR-API migration: TenantService::getTenantByGroupId() still uses getObjects() The PR description acknowledges that Since this PR is scoped to repair OR-API drift, leaving a known broken call site in-tree is an incomplete fix. Add a |
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [CONCERN] PHP The filter array is constructed as This is likely intentional (callers should not override register/schema), but it creates a silent footgun: a caller passing those keys will see no error and get unexpected query results. At minimum, add a brief comment explaining the merge order is deliberate. |
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [CONCERN] Seed deletion not verified for reverse references to deleted parafeeractie slugs Three If any surviving seed object references these slugs (e.g. a workflow step, a status record, or a voorstel body field), the deletion creates new dangling references in the opposite direction. Run |
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [CONCERN] VisualWorkflowEditor commented out without a tracking issue
Fix: open a tracking issue (e.g. 'Replace @vue-flow with Vue-2-compatible library or migrate to Vue 3'), reference the issue number in the comment, and optionally add a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[BLOCKER]
hasRow()called on flat findAll() array — shape mismatch may cause unchecked re-seeding$existingis now the flat array returned byfindAll()(a list of entity objects). The oldgetObjects()returned a paginated wrapper['objects' => [...], 'total' => N]. The call$this->hasRow($existing)on line 61 is unchanged in this PR.If
hasRow()internally checks$existing['objects']or treats a non-empty paginated wrapper as truthy, it will now receive an unexpected shape and silently returnfalseeven when an active LHS matrix already exists — causing the repair step to overwrite live matrix data on every run ofphp occ maintenance:repair.The diff does not show the body of
hasRow(). Before merging, verify thathasRow()correctly handles a flat PHP array. If it does not, inline the check ascount($existing) > 0or updatehasRow()accordingly.