Tag mode not working properly about angular-selectize HOT 7 CLOSED

Thanks! glad you like it.

If you could create a Plnkr demonstrating the problem that would help. I
went ahead and created this one to demonstrate how to do what I think
you're trying to do: http://plnkr.co/edit/rD0AGP?p=preview

On Fri, May 30, 2014 at 10:21 AM, Ben Pate [email protected] wrote:

First, fantastic code. And thank you very much for posting this publicly.
I'm working to incorporate this into a project. Hopefully, you've got time
to check this out, and at least point me in the right direction to fix this.

Here's the issue: When use a selectize widget in tag mode, the first
tag is added correctly, but subsequent tags not added separately, but
concatenated into the value of the original tag. I'm too new to AngularJS
directives to make a patch for this, but I can at least document what I'm
seeing in my environment:
Javascript Controller

$scope.contacts = contacts; $scope.emailConfig = {
create:true,
valueField: 'contactId',
labelField: 'name',
maxItems: 100};

HTML View

Screenshots: 1. The first tag works great: (yay!)

[image: single-tag]
https://cloud.githubusercontent.com/assets/4381040/3133715/4c734e20-e81d-11e3-8fcb-297be4c4086d.png
2. But the second tag doesn't :(

[image: double-tags]
https://cloud.githubusercontent.com/assets/4381040/3133714/4c7120dc-e81d-11e3-9a57-af99304a2fbb.png
3. And turns ugly with values instead of labels

Here, I'm using values for each record instead of names
(valueField:'contactId'). The problem is really apparent when I do this:
[image: three-tags]
https://cloud.githubusercontent.com/assets/4381040/3133802/31f1b644-e81e-11e3-9c5c-560bdfaf3a83.png

—
Reply to this email directly or view it on GitHub
#2.

from angular-selectize.

You're awesome. It looks like your demo works great, so it's very possibly just a bug in my code. Thanks for the demo!

I'm offline for now, but will try to get a plnkr together shortly.

from angular-selectize.

Cool. Sounds good.

On Fri, May 30, 2014 at 4:22 PM, Ben Pate [email protected] wrote:

You're awesome. It looks like your demo works great, so it's very possibly
just a bug in my code. Thanks for the demo!

I'm offline for now, but will try to get a plnkr together shortly.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

from angular-selectize.

Looks like I had some time :) Here's my Plunk:

http://plnkr.co/edit/rdhjZFCM5tpBJabHnSdX?p=preview

I'm guessing that some of the other libraries I'm using are causing some kind of conflict. My first hunch is that it's the way that $resource is loading the contents asynchronously.

Again, thanks so much for spending your time to check this out. It's really appreciated.

from angular-selectize.

I think I found the problem. The directive needs but
you're using .

On Fri, May 30, 2014 at 6:41 PM, Ben Pate [email protected] wrote:

Looks like I had some time :) Here's my Plunk:

http://plnkr.co/edit/rdhjZFCM5tpBJabHnSdX?p=preview

I'm guessing that some of the other libraries I'm using are causing some
kind of conflict. My first hunch is that it's the way that $resource is
loading the contents asynchronously.

Again, thanks so much for spending your time to check this out. It's
really appreciated.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

from angular-selectize.

Yes. That works beautifully. So, selectize.js works with either or , but the angular-selectize directive only works with . Sorry I missed that. Best wishes!

edited: Not sure how to close this ticket. I think you may need to do that part. :)

from angular-selectize.

Ya, perhaps I should make a big note on the GitHub Readme.

On Sat, May 31, 2014 at 2:06 PM, Ben Pate [email protected] wrote:

Yes. That works beautifully. So, selectize.js works with either or , but
the angular-selectize directive only works with . Sorry I missed that.
Best wishes!

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

from angular-selectize.