Open mischkl opened 4 years ago
devversion
commented
4 years ago Seems like a reasonable feature request to me. I don't think we can handle the label in a good way as that is usually disconnected from the select (as it is adjacent and part of the form-field).
Though I can definitely see us handling the selected (display) value and placeholder (need to figure out how we can access the placeholder as that one is not always rendered)
angular-robot[bot]
commented
2 years ago Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
angular-robot[bot]
commented
2 years ago Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
Feature Description
At the moment the MatSelectHarness can only be retrieved by selector. It would be helpful if other options were available such as label, placeholder, text, or form control name.
Use Case
Solely relying on selectors to get MatSelectHarness requires the templates to be designed in a specific way, for instance with custom attributes - this feature would make developers' lives easier by avoiding that requirement. Other harnesses such as MatInputHarness allow getting the harness according to placeholder and value text. So it seems logical to expect that the MatSelectHarness would also offer this convenience.