Skip to content

fix(ng-update): type imports not migrated to secondary entry-points #16108

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 24, 2019

Conversation

devversion
Copy link
Member

The V8 import migration does not seem to properly handle the migration
of type imports as these don't have an actual Symbol value declaration
but rather just a plain declaration. We need to support both (value declaration
for real values) and fall back to the first non-value declaration for types.

The V8 import migration does not seem to properly handle the migration
of type imports as these don't have an actual Symbol `value` declaration
but rather just a plain declaration. We need to support both (value declaration
for real values) and fall back to the first non-value declaration for types.
@devversion devversion added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful pr: merge safe target: patch This PR is targeted for the next patch release labels May 24, 2019
@devversion devversion requested a review from jelbourn as a code owner May 24, 2019 08:23
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 24, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels May 24, 2019
@mmalerba mmalerba merged commit dc51691 into angular:master May 24, 2019
RudolfFrederiksen pushed a commit to RudolfFrederiksen/material2 that referenced this pull request Jun 21, 2019
…ngular#16108)

The V8 import migration does not seem to properly handle the migration
of type imports as these don't have an actual Symbol `value` declaration
but rather just a plain declaration. We need to support both (value declaration
for real values) and fall back to the first non-value declaration for types.
@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 Sep 10, 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.

4 participants