Backend-filtering not compatible?

[lkgarrison]

I would like to perform filtering on the back-end (provide suggestions for tags as the user types). The problem is that using the "filter" property on the ember-selectize resultings in hiding the previously selected tags when text is typed into the box after a tag is selected. Is there a different way that I am overlooking to update the options/results to choose from in the select via a call to my application's backend, using the current text the user typed as the text to filter by on my back-end?

[miguelcobain]

Does this help?
#81

[lkgarrison]

Very close, but I need a way to clear the "filter" that is still active. I have tags such as "nodejs" and "expressjs" that my back-end returns as I type in the select box. If I type "expr", and then select the option "expressjs", all is good - the tag appears in the select box as expected. I would then expect to be able to type a second tag in the box, next to the existing tag. However, as soon as I do so, a new filter is applied and the "expressjs" tag disappears. As i type "node" and then select the "nodejs" tag option, I only have 1 tag visible in the select. If I click the "x" on the "nodejs" tag, then start typing "exp", then the "express tag becomes visible again. It was there the whole time, but the internal filter is making it disappear whenever the current filter doesn't match the existing tags.