Autocomplete optionSelections to return one observable rather than an array

[christikaes]

Bug, feature request, or proposal:

It would be easier to consume optionSelections if it returned a single observable that streamed which option was selected rather than an array, or alternatively emitted a change event like mdSelect.

The modification would be to this function:
https://github.com/angular/material2/blob/master/src/lib/autocomplete/autocomplete-trigger.ts#L163

What is the expected behavior?

The user should be able to call

trigger.optionSelections.subscribe(optionSelected => {
    // do stuff with the selected option
})

or alternatively listen to a change event

What is the current behavior?

Currently, to listen to what option changed, I have to subscribe to each one of the observes in optionSelections[]

Is there anything else we should know?

You guys are awesome :D I love angular2 material!!
🎆 Wooo autocomplete 🎆

[crisbeto]

FWIW, you can still do Observable.merge(...trigger.optionSelections) to subscribe to all of them at once.

[sumpton]

Material2 is great. Thank you.

Is there an example of how to use MdAutocompleteTrigger and optionSelections?

[crisbeto]

@sumpton you can query for it with @ViewChild(mdAutocompleteTrigger) which then gives you access to the option selections. We should probably do a separate change event at some point.

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