Store lists of objects that pass name attribute, rather than passing actual strings.

[CarbonComputed]

Why restrict pushing strings? Why not push a "tag" object. All other attributes on the tag can remain the same, but when displaying it access the tags name field. For example, opposed to doing
tag = privateMethods.trimTag(tag, opts.delimiterChars);
Do this:
tag.name = privateMethods.trimTag(tag.name, opts.delimiterChars);

I know I would use this because usually a tag represents more than just a name. A tag might have an json associated with it for example. I'm using a modified version of this plugin on my site and the tags represent tag models in my database. These have more attributes than just a string: description, image, etc. This could be useful for web applications that associate tags with attributed data plus a name, not just a string.

[noirbizarre]

+1

It's really important because sometime we have to store IDs or other attributtes.

[johnnyshields]

Hi guys, as I've said in other threads if someone can raise a PR for this we'll accept it. Now that we've switched to Twitter Typeahead it should be more easily achieved than when we were on the legacy Bootstrap Typeahead.