Skip to content
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

fix(@angular-devkit/schematics): fully resolve schematic entries within packages #17092

Merged
merged 1 commit into from
Mar 30, 2020

Conversation

clydin
Copy link
Member

@clydin clydin commented Feb 26, 2020

Fixes: #17085

@clydin clydin added the target: patch This PR is targeted for the next patch release label Mar 23, 2020
@clydin clydin marked this pull request as ready for review March 24, 2020 20:09
@clydin clydin requested review from alan-agius4 and removed request for alan-agius4 March 24, 2020 20:09
@alan-agius4 alan-agius4 self-requested a review March 25, 2020 17:34
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Mar 30, 2020
@kyliau kyliau merged commit ea3d9e0 into angular:master Mar 30, 2020
@clydin clydin deleted the resolve-schematic-collection branch March 30, 2020 17:31
@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 Apr 30, 2020
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.

Regression: unable to resolve schematics via package name
4 participants