Added some unit test to prevent problems in the future.
Still don't know if this is the best way to validate the resetSearch function, would love to see some feedback 😄

1,226 test/select.spec.js
630 additions, 596 deletions not shown because the diff is too large. Please use a local Git client to view these changes.

Did you intend to make that many changes? I've not pulled down to review yet just wondering if maybe you broke some whitespacing or something.

And, as always, thanks for your work/patience 👍

@user378230 think I used auto format reverted the commit and added the new tests. These will check if the multiple ui-select is working with resetSearchInput.

Just read the wiki and there resetSearchInput is default set true. You want me to change the code or the wiki?

Thanks for the fix @Jefiozie

@aaronroberson any chance this can be merged and a new release cut?

Merged. Will test to see if the travis hooks will update the version and publish to NPM.

thanks @aaronroberson looks like Travis failed to publish with:

Skipping a deployment with the script provider because this is not a tagged commit
Skipping a deployment with the npm provider because this is not a tagged commit

@aaronroberson, thanks for merging this 😄. I will update the wiki as the resetsearchinput is default false.

Thanks @timelf123 and @Jefiozie! v0.19.3 is now available :D

thanks @aaronroberson for the quick merge! can you git tag 0.19.3 && git push --tags?

We should really revert the default back to true

@Jefiozie Can you create a PR to revert the default to true?

@aaronroberson Sure no problem!