triggerValue of MdSelect as @Input

[RobYed]

Bug, feature request, or proposal:

feature request

What is the expected behavior?

I'd like to be able to set the triggerValue of a MdSelect. The use case is, that I wish to display a triggerValue which is different from the MdOption's textContent (which is automatically taken).
Therefore it would be great, if triggerValue would be an @Input of MdSelect.

What is the current behavior?

triggerValue is a readonly property of MdSelect. Consequently there is no possibility to manually set a triggerValue (if there is some, let me know!).

What is the use-case or motivation for changing an existing behavior?

I use a MdOption to set a filter for some search. It shows the option's values and their count of occurences. When an option is selected, the count of occurences will appear in the MdSelect's triggerValue, but without styling, therefore looking fairly misplaced.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular: 4.2.2
Material: 2.0.0-beta.6

Is there anything else we should know?

If this is a feature you consider to add, I could try to implement it and open a PR.

And of course, big thanks for this great project! I was also using the AngularJS version of Material and it has always been a pleasure to use it!!

[willshowell]

This seems kinda like #2275 (with PR at #3341).

[RobYed]

Yeah, that one would fix my issue. Thanks!

[angular-automatic-lock-bot]

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.}