migrate-antd-v6

To migrate antd v3 to v6 without regressions, scope changes to a single file or route and capture before/after Playwright screenshots of real rendered routes. This verifies loading states and interaction behaviors, halting at a signed commit for owner approval before changes are finalized.

The best way to update deprecated antdV3 imports flagged by Sonar alerts is targeted single-file migration. Instead of repo-wide sweeping, it scopes work to the flagged component, matching existing antd v6 patterns to ensure migrated code fits seamlessly with the codebase.

Playwright is used for visual regression testing during antd v6 migration by capturing before/after screenshots of real rendered routes. It enforces real user interaction behavior checks to catch functional and visual regressions before committing code changes.

You cannot perform repo-wide sweeping of remaining antdV3 holdouts with this approach. Migration is strictly scoped to a single specified target file or route, preventing unvetted code changes and limiting the blast radius of potential regressions.

To ensure migrated antd v6 code matches your repository conventions, the migration process discovers and matches the target repository's existing antd v6 code patterns. This guarantees the updated component fits seamlessly into the current codebase without style conflicts.

You need to halt an antd v3 to v6 component migration at a signed commit command for owner approval. This prevents unvetted code changes from being merged, ensuring visual and behavior regressions are reviewed before finalizing the migration.