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(ng-update): imports to MatProgressSpinnerModule not migrated #17717

Merged

Conversation

devversion
Copy link
Member

For v9 we generated a mapping of symbols and their corresponding secondary
entry-points. This map was based on the public API goldens we generate with
ts-api-guardian. Unfortunately ts-api-guardian has known limitations with
aliased exports which do not have the export keyword on the actual declaration.

This means that we currently do not have a mapping for such exports. Temporarily
changing ts-api-guardian to handle such cases showed that the progress-bar
module is the only instance in the project.

Fixes #17715.

Note: This actually brings us to the point where we should re-consider the effort of switching to api-extractor from Microsoft eventually. This was already planned in the past, but we prioritized other things IIRC. The current API goldens are not guaranteed to be complete.

For v9 we generated a mapping of symbols and their corresponding secondary
entry-points. This map was based on the public API goldens we generate with
ts-api-guardian. Unfortunately ts-api-guardian has known limitations with
aliased exports which do not have the export keyword on the actual declaration.

This means that we currently do not have a mapping for such exports. Temporarily
changing ts-api-guardian to handle such cases showed that the progress-bar module is the only instance in the project.

Fixes angular#17715.
@devversion devversion added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release labels Nov 15, 2019
@devversion devversion added this to the 9.0.0 milestone Nov 15, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 15, 2019
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 15, 2019
Copy link
Contributor

@andrewseguin andrewseguin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andrewseguin andrewseguin merged commit 3acd6c1 into angular:master Nov 15, 2019
@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 Dec 16, 2019
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 cla: yes PR author has agreed to Google's Contributor License Agreement P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng update v9 "MatProgressSpinnerModule" was not found in the Material library.
4 participants