Skip to content

Feat/schematics 49#1441

Draft
mistrykaran91 wants to merge 5 commits intomainfrom
feat/schematics-49
Draft

Feat/schematics 49#1441
mistrykaran91 wants to merge 5 commits intomainfrom
feat/schematics-49

Conversation

@mistrykaran91
Copy link
Member

@mistrykaran91 mistrykaran91 commented Feb 4, 2026

Closes #1401


Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces the schematics for migrating from v48 to v49. The changes are comprehensive, covering component, input, and output renames, as well as more complex pattern-based replacements, and include a solid suite of new tests. However, I've identified two critical issues in the utility functions that could break existing migrations or fail in complex scenarios. Please see my detailed comments.

Copy link
Member

@spike-rabbit spike-rabbit left a comment

Choose a reason for hiding this comment

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

Please try to break it down into smaller PRs.

  1. the refactoring from my comment above
  2. update the migration data
  3. add new features, which are not covered yet by the current capabilities of elementMigrationRule

@github-actions
Copy link

github-actions bot commented Feb 4, 2026

@github-actions
Copy link

github-actions bot commented Feb 5, 2026

Code Coverage

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.

Element migration schematics for v49

2 participants