Invalid filtering due to using "RegExp.test()"

[kfbishop]

After banging my head for most of a day, I've stumbled upon an odd side-effect caused by using "RegExp.text() in select.ts:filter() (line ~515). Seems RegExp keeps a back reference from the last test, which negates the next test! Changing the code to use .match() resolves this issue, at the theoretical expense of performance.

This can be verified / tested using the following plunker
Ng2 test() v match() test

References:

• MDN text() - test() called multiple times on the same global regular expression instance will advance past the previous match
• S/O (final answer)

[kfbishop]

components/select/select.ts: Line 517

Was: .filter(option => query.test(option.text) &&
To be: .filter(option => option.text.match(query) &&

[valorkin]

@kfbishop https://github.com/valor-software/ng2-select/pull/57/commits
there a lot of commits
from which I will not be able to generate changelog