Array of strings

[sebastiannm]

trafficstars

Hi, I worked on a feature that is very much requested.

Turning off itemIsObject (on by default for backwards compatibility) will create an array of strings instead of objects. I'm using it in production without problems.

[mohag519]

Excellent thanks!

[nescalante]

+1 seems to solve https://github.com/mbenford/ngTagsInput/issues/666

[jrdn91]

Any plans on when this will be merged into master? I'm working with this directive right now but I'm having to do serialization because I need an array of strings rather than an array of objects

[gustavodegeus]

+1

[mjmarianetti]

+1

[repalogic]

@sebastiannm Could you make your repository public so that it might be possible to merge your changes in an own fork. So your changes would be reusable by others until the pull request will be accepted here.

[nescalante]

@repalogic: https://github.com/Nex9/ngTagsInput

[matthew-mahony]

I have a problem where auto complete does not work when I set item-is-object to false. When typing in the tags field, I get an error in the console "array1.filter is not a function".

I fixed the error by changing: getDifference(items, tags); to getDifference(items.data || items, tags);

When item-is-object is enabled, the items.data is used when available, but that check is missing when using simple arrays.

[ronaldohoch]

Hello.

It will be released soon in bower?

[tkserver]

Thanks @nescalante this solved my problem! Needed an array strings, not objects. I would like to know when this is merged with the original base code.

[edmedo]

Hi, are we any closer to getting this merged? Seems to me this is a requirement for many people. I'd prefer not to have to transform my model the entire time to hack around this problem :-/