Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.

Conversation

chenlijun99
Copy link
Contributor

@chenlijun99 chenlijun99 commented Mar 10, 2018

PR Checklist

Please check that your PR fulfills the following requirements:

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

When using ng-model-options="{ 'trackBy': '$value.someProperty' }" on md-select, ng-change is triggered when the selected option's object is not equal to the one of the model (the comparison is done with angular.equals which compares recursively all the properties of the object).
Issue Number: #11108

What is the new behavior?

ng-change is triggered when the tracked property of the model is different from the selected option.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@googlebot googlebot added the cla: yes PR author has signed Google's CLA: https://opensource.google.com/docs/cla/ label Mar 10, 2018
@Splaktar Splaktar self-requested a review March 13, 2018 07:46
@Splaktar Splaktar self-assigned this Mar 13, 2018
Copy link
Contributor

@Splaktar Splaktar left a comment

Choose a reason for hiding this comment

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

Thank you for sending this PR!

I just had the one minor typo comment. Manual testing looks good.

One other thing, can you please update the commit to more closely follow the commit guidelines especially with the Closes line being on the last line? Thank you.

@Splaktar Splaktar added in progress Mainly for in progress PRs, but may be used for issues that require multiple PRs type: bug P4: minor Minor issues. May not be fixed without community contributions. labels Mar 13, 2018
@Splaktar Splaktar added this to the 1.1.9 milestone Mar 13, 2018
@chenlijun99 chenlijun99 reopened this Mar 13, 2018
@chenlijun99
Copy link
Contributor Author

chenlijun99 commented Mar 13, 2018

@Splaktar Do you have any clue on why is the travis ci build failing?
I've only fixed the typo and changed the commit message.

It seems to be failing on other pull requests as well.

@Splaktar
Copy link
Contributor

TravisCI had a significant outage last night around that time. I've restarted the tests.

@Splaktar
Copy link
Contributor

I need to improve the commit message guidelines, sorry for the confusion. I'll try to add some examples to them.

I believe that the footer needs to use the format Closes #11108 and not Closes issue #11108. This is how the feature of GitHub works.

@chenlijun99
Copy link
Contributor Author

I've changed the commit message.

But the travis ci build seems to be still failing.

@Splaktar
Copy link
Contributor

It also looks like there is an issue with the AngularJS snapshot builds. I'll check with the team.

@Splaktar Splaktar removed the in progress Mainly for in progress PRs, but may be used for issues that require multiple PRs label Mar 13, 2018
Copy link
Contributor

@Splaktar Splaktar left a comment

Choose a reason for hiding this comment

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

LGTM

@Splaktar Splaktar added the pr: merge ready This PR is ready for a caretaker to review label Mar 13, 2018
@Splaktar Splaktar modified the milestones: 1.1.9, 1.1.8 Mar 13, 2018
@Splaktar
Copy link
Contributor

It's possible that their snapshot somehow got corrupted by the TravisCI outage. I'll let you know when I find out more.

@chenlijun99
Copy link
Contributor Author

Which would be the best way to integrate this fix into my project before the next version of angular material is released?

@Splaktar
Copy link
Contributor

Once we get it merged, there will be a build with a hash on it that you will be able to install directly via NPM.

// if they have the same length, then they are different
// if an item in the newVal array can't be found in the prevVal
return newVal.every(function(newValItem) {
return !!prevVal.find(function(prevValItem) {
Copy link
Member

Choose a reason for hiding this comment

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

Not sure what the supported browsers are, but make sure they all implement .find() (IE does not for example).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Gosh! I've always thought find was supported since IE 9...

@Splaktar Splaktar modified the milestones: 1.1.13, 1.1.14 Feb 10, 2019
@Splaktar Splaktar modified the milestones: 1.1.14, 1.1.15 Mar 14, 2019
@Splaktar Splaktar modified the milestones: 1.1.15, 1.1.16, 1.1.18, 1.1.19 Mar 29, 2019
@Splaktar Splaktar removed Blocked Progress on this issue is blocked. Primarily used for PRs that are blocked by presubmit feedback. pr: presubmit-failures labels May 18, 2019
@Splaktar Splaktar dismissed josephperrott’s stale review May 18, 2019 18:44

Concerns have been addressed.

@Splaktar
Copy link
Contributor

It looks as though the internal issues have been resolved and this may be able to get into 1.1.19.

@Splaktar Splaktar modified the milestones: 1.1.19, 1.1.21 May 30, 2019
@Splaktar Splaktar assigned mmalerba and unassigned josephperrott Jun 13, 2019
@Splaktar Splaktar modified the milestones: 1.1.21, 1.1.22 Aug 15, 2019
@Splaktar Splaktar modified the milestones: 1.1.22, 1.1.23 Oct 22, 2019
@Splaktar Splaktar modified the milestones: 1.1.23, 1.1.22 Mar 4, 2020
@Splaktar Splaktar requested a review from jelbourn March 4, 2020 19:14
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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has signed Google's CLA: https://opensource.google.com/docs/cla/ P3: important Important issues that really should be fixed when possible. pr: lgtm This PR has been approved by the reviewer pr: merge ready This PR is ready for a caretaker to review type: bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants