Skip to content

fix(@angular/cli): register schematic aliases when providing collection name in ng generate #24542

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
Jan 13, 2023

Conversation

alan-agius4
Copy link
Collaborator

Previously, schematic aliases were not registered when a collection name was provided to ng generate. Example: ng generate c where c is an alias for component would work, but ng generate @schematics/angular:c would fail. This commits fixes the schematic registration to handle the latter case.

Closes #24518

@alan-agius4 alan-agius4 added target: patch This PR is targeted for the next patch release action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 13, 2023
@alan-agius4 alan-agius4 force-pushed the schematic-aliases branch 2 times, most recently from 36d712e to 16197a0 Compare January 13, 2023 13:13
@alan-agius4 alan-agius4 requested a review from clydin January 13, 2023 13:13
@alan-agius4 alan-agius4 changed the title fix(@angular/cli): register schematic aliases when providing collection name in ng generate. fix(@angular/cli): register schematic aliases when providing collection name in ng generate Jan 13, 2023
@alan-agius4 alan-agius4 removed the request for review from clydin January 13, 2023 14:07
@alan-agius4 alan-agius4 added state: WIP and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 13, 2023
…on name in `ng generate`

Previously, schematic aliases were not registered when a collection name was provided to `ng generate`.  Example: `ng generate c` where `c` is an alias for `component` would work, but `ng generate @schematics/angular:c` would fail. This commits fixes the schematic registration to handle the latter case.

Closes angular#24518
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed state: WIP labels Jan 13, 2023
@angular-robot angular-robot bot merged commit 3ebb195 into angular:main Jan 13, 2023
@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 Feb 13, 2023
@alan-agius4 alan-agius4 deleted the schematic-aliases branch June 9, 2023 15:03
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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Passing an argument to an aliased custom ng g schematic, don't recognize the argument
2 participants