nx
nx copied to clipboard
fix(angular): expand nx tokens in project configurations when running schematic migrations
Current Behavior
Running Angular CLI schematic migrations that update project configurations that contain Nx tokens (e.g. {workspaceRoot}, {projectRoot}, {projectName}) does not work correctly. The schematic migrations receive the project configuration option values with the non-expanded tokens, which is not something handled.
Expected Behavior
The Nx adapter for Angular should expand Nx tokens in project configurations so schematic migrations can correctly process them. When writing the project configuration back, the tokens should be restored on a best-effort basis.
Related Issue(s)
Fixes #29052