-
Notifications
You must be signed in to change notification settings - Fork 21
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
MatSelect fix #1248
MatSelect fix #1248
Conversation
Deployed to https://test-deployment-pr-1248.herokuapp.com/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
🎉 This PR is included in version 3.6.0-master.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
see issue: #1244
Background: Angular compares the value of a
MatSelect
with the options that are available in order to find the one that is currently selected. In our case both these values are loaded from the config but in some cases the config changes and therefore the objects might have different references. In this case Angular is not able to match the selected value with the options and does not display anything.[compareWith]
allows to overwrite this behavior which we can use to compare the enum values more deeply (source).Visible/Frontend Changes
MatSelect
with configurable enum are correctly displayed when page has just loaded.Architectural/Backend Changes
compareWith
to correctly match options to values inMatSelect