Skip to content

fix(@angular/cli): resolve relative schematic from angular.json instead of current working directory #23138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 17, 2022

Conversation

alan-agius4
Copy link
Collaborator

Relative schematics referenced in angular.json schematicCollections and defaultCollection were always resolved from the current working directory, which is not correct and caused the collection not to be resolved when the this is different from the location of the workspace config.

Closes #23136

…tead of current working directory

Relative schematics referenced in `angular.json` `schematicCollections` and `defaultCollection` were always resolved from the current working directory, which is not correct and caused the collection not to be resolved when the this is different from the location of the workspace config.

Closes angular#23136
@alan-agius4 alan-agius4 added action: review The PR is still awaiting reviews from at least one requested reviewer target: rc This PR is targeted for the next release-candidate labels May 16, 2022
@alan-agius4 alan-agius4 force-pushed the cwd-schematic-resolution branch from 745a76e to 1155e50 Compare May 16, 2022 08:28
@alan-agius4 alan-agius4 requested a review from clydin May 16, 2022 08:41
@clydin clydin added this to the v14 milestone May 17, 2022
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels May 17, 2022
@dgp1130 dgp1130 merged commit c71832f into angular:main May 17, 2022
@alan-agius4 alan-agius4 deleted the cwd-schematic-resolution branch May 17, 2022 21:38
@kvart714
Copy link

@alan-agius4 Tell me, please, will the fix be published in version 13.x.x?

@alan-agius4
Copy link
Collaborator Author

@alan-agius4 Tell me, please, will the fix be published in version 13.x.x?

I have opened a PR that contains a patch version for this #23167

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

defaultCollection is relative to where cmd is run not angular.json
4 participants