Skip to content

refactor(migrations): add a migration for optional chainings#68352

Draft
JeanMeche wants to merge 1 commit intoangular:mainfrom
JeanMeche:safe-navigation-migration
Draft

refactor(migrations): add a migration for optional chainings#68352
JeanMeche wants to merge 1 commit intoangular:mainfrom
JeanMeche:safe-navigation-migration

Conversation

@JeanMeche
Copy link
Copy Markdown
Member

#68084 introduces semantic change for optional chainings to match the native behavior.

This migration ensure that existing code is wrapped by the $safeNavigationMigration magic function when necessary to maintain the pre-exisiting behavior of exisiting optional chaining expressions.

@angular-robot angular-robot Bot added the area: migrations Issues related to `ng update`/`ng generate` migrations label Apr 23, 2026
@ngbot ngbot Bot added this to the Backlog milestone Apr 23, 2026
@JeanMeche JeanMeche force-pushed the safe-navigation-migration branch 13 times, most recently from 5bb81c9 to 2275f12 Compare April 24, 2026 13:18
This migration ensure that existing code is wrapped by the `$safeNavigationMigration` magic function when necessary to maintain the pre-exisiting behavior of exisiting optional chaining expressions.
@JeanMeche JeanMeche force-pushed the safe-navigation-migration branch from 2275f12 to ab2f315 Compare April 26, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: migrations Issues related to `ng update`/`ng generate` migrations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant