Skip to content

refactor(schematics): clear migration data for class members, components, elements, and symbols#1976

Draft
mistrykaran91 wants to merge 1 commit intomainfrom
refactor/clean-up-schematics-data
Draft

refactor(schematics): clear migration data for class members, components, elements, and symbols#1976
mistrykaran91 wants to merge 1 commit intomainfrom
refactor/clean-up-schematics-data

Conversation

@mistrykaran91
Copy link
Copy Markdown
Member

@mistrykaran91 mistrykaran91 commented Apr 29, 2026

  • Clear migration data for class members, components, elements, and symbols

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

Copy link
Copy Markdown
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 clears all migration data arrays for version 49, including class member replacements, component property names, element class changes, element selectors, symbol removals, and symbol renaming. The feedback indicates that emptying these arrays while the migration schematic is active will disable automated updates, leading to breaking changes and compilation errors for users. Specifically, the removal of symbol renaming and element selector transformations will force manual updates, undermining the purpose of the migration schematics.

propertyReplacements: [{ property: 'initialState', replacement: '${expression}.inputValues' }]
}
];
export const CLASS_MEMBER_REPLACEMENTS_MIGRATION: ClassMemberReplacementInstruction[] = [];
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

Clearing the migration data while the migration-v49 schematic remains active in migration.json effectively disables all automated updates for this version. This action will result in breaking changes for users performing an ng update, as the expected transformations (such as property renamings and class member replacements) will not be applied. If these migrations are being moved to a different version or a new mechanism, please ensure that the update path remains intact for users transitioning to v49.

]
}
];
export const SYMBOL_RENAMING_MIGRATION: SymbolRenamingInstruction[] = [];
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

Removing the symbol renaming data is particularly impactful as it includes the migration from Simpl prefixed symbols to Si (e.g., SimplChartsNgModule to SiChartsNgModule). Without this data, users updating to v49 will encounter numerous compilation errors that would otherwise be handled automatically by the schematic.

]
}
];
export const ELEMENT_SELECTORS_MIGRATION: ElementSelectorInstruction[] = [];
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

Clearing this array removes the automatic migration of deprecated element selectors, such as si-unauthorized-page to si-info-page. This will require users to manually update their templates, which contradicts the purpose of the provided migration schematic.

@spike-rabbit spike-rabbit added this to the 50.0.0 milestone Apr 29, 2026
@spike-rabbit spike-rabbit added the breaking-changes Marks issues and PRs that are breaking the API label Apr 29, 2026
@mistrykaran91 mistrykaran91 force-pushed the refactor/clean-up-schematics-data branch from e54611b to 4f381d6 Compare May 2, 2026 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking-changes Marks issues and PRs that are breaking the API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants