Ruben Vermeersch
Ruben Vermeersch
Nope, not yet. Would happily merge a pull request for it. As a workaround, use a scope watch on the variable that you use in the `ng-model` field.
Err wait, this might just work automatically. Have you tried it?
Cool! Can you add a test case as well?
I'd love to, but I have no plans to do so myself until it comes out of beta. Will happily start accepting patches on a branch though. On 10 Mar...
@rbatllet I'm guessing that it'll be quite a bit of work. Given that select2 3.x works perfectly fine, it's not a priority for us to upgrade (plenty of other work...
Am currently traveling but will do so soon. Thanks for picking this up! On Sep 2, 2015 8:16 AM, "Fredrik Wollsén" [email protected] wrote: > It's basically "done". > https://github.com/motin/angular-select2/tree/select2-4.0-support-wip JS...
I've pushed a `v4` branch, pull requests are welcome. Once this branch is stable, we'll merge it to master and we'll split off a maintenance branch for the older select2...
This is an Angular bug. Same reason why you can't have `filter` in there. I wish there was a way on how to support this (a scope variable to a...
> which is a real dealbreaker for a production environment. Nah, we're using it in production without any issues. It's just a set of limitations you have to be aware...
I can't merge this: the files in `dist/` are generated from the ones in `src/`, so you'll need to add your changes there. Also, I'd like to have a test...