Skip to content

fix(ng-update): do not report form-field breaking change from v6 #16161

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

Conversation

devversion
Copy link
Member

The misc rules currently run for every migration, but the one for the
shouldLabelFloat was apparently using a wrong check that has
been added back in the days when we pulled out the standalone
migration tool into the material2 repository.

While being at it, we are fixing that invalid check and limit
the misc migration to the V6 upgrade target version.

Fixes #16143

The misc rules currently run for every migration, but the one for the
`shouldLabelFloat` was apparently using a wrong check that has
been added back in the days when we pulled out the standalone
migration tool into the material2 repository.

While being at it, we are fixing that invalid check and limit
the misc migration to the V6 upgrade target version.

Fixes angular#16143
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels May 30, 2019
@devversion devversion requested a review from jelbourn as a code owner May 30, 2019 11:26
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 30, 2019
@andrewseguin andrewseguin added the P4 A relatively minor issue that is not relevant to core functions label May 30, 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 30, 2019
@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent and removed P4 A relatively minor issue that is not relevant to core functions labels May 30, 2019
@andrewseguin andrewseguin merged commit 2adf629 into angular:master May 31, 2019
josephperrott pushed a commit that referenced this pull request Jun 10, 2019
)

The misc rules currently run for every migration, but the one for the
`shouldLabelFloat` was apparently using a wrong check that has
been added back in the days when we pulled out the standalone
migration tool into the material2 repository.

While being at it, we are fixing that invalid check and limit
the misc migration to the V6 upgrade target version.

Fixes #16143
RudolfFrederiksen pushed a commit to RudolfFrederiksen/material2 that referenced this pull request Jun 21, 2019
…ular#16161)

The misc rules currently run for every migration, but the one for the
`shouldLabelFloat` was apparently using a wrong check that has
been added back in the days when we pulled out the standalone
migration tool into the material2 repository.

While being at it, we are fixing that invalid check and limit
the misc migration to the V6 upgrade target version.

Fixes angular#16143
@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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

'shouldLabelFloat' Error during ng update @angular/material
4 participants