Skip to content

fix(process-map): migrate follow-ups from the #438 review - #453

Merged
MendixMau merged 1 commit into
release/v1.0from
fix/process-map-migrate-followup
Oct 16, 2026
Merged

MendixMau merged 1 commit into
release/v1.0from
fix/process-map-migrate-followup

Conversation

@MendixMau

Copy link
Copy Markdown
Owner

Three non-blocking regressions in the process-map migrate step, from the #438 re-review.

  1. The model key was patched with a regex that hits the first "anchors": "..." at any depth. After the rewrite the result is now parsed and the top-level key checked; if it did not change, the whole model is re-written with the key set. The output only says "only that key was changed" when that is true.
  2. An old file with "targets": "P1-02" (a string) crashed migrate. A string is now a one-item list.
  3. Unfilled entries (no targets) already in the current anchors file were dropped silently. They are now listed, like entries with no target in the old file.

Tests in tests/wave2/test-process-map-field.sh, one group per item (6 of the new checks fail without the fix). process-map tests, brd-report-process-map, check-portability and check-pr-discipline are clean.

🤖 Generated with Claude Code

Check the top-level anchors key changed after the regex rewrite and fall back
to re-writing the model otherwise; accept a string targets value; list
unfilled entries of the current anchors file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MendixMau
MendixMau merged commit 32266fa into release/v1.0 Oct 16, 2026
2 checks passed
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.

1 participant