Skip to content
This repository has been archived by the owner on Nov 22, 2021. It is now read-only.

Allow the tag delimiter to be configured explicitly #95

Closed
JAndritsch opened this issue Mar 11, 2014 · 6 comments
Closed

Allow the tag delimiter to be configured explicitly #95

JAndritsch opened this issue Mar 11, 2014 · 6 comments

Comments

@JAndritsch
Copy link

As of right now, tags can only be created on comma, enter, space, or blur. This can be configured via these attributes:

[add-on-enter="{boolean}"}
[add-on-space="{boolean}"]
[add-on-comma="{boolean}"]
[add-on-blur="{boolean}"]

I think it be useful if there was a configuration for a list of extra tag delimiters that the user could choose. You might also be able to get rid of add-on-space and add-on-comma.

Example:

scope.addTagOnCharacters = [",",     ";",    "#",    " "]
add-on-character="addTagOnCharacters"

You could even go as far as allowing the user to specify which events should trigger the code to add a tag.

Example:

scope.addTagOnEvents = ["blur",     "click",    "focus",    "hover"]
add-on-events="addTagOnEvents"

That would also allow adding tags on custom user events.

Example:

scope.addTagOnEvents = ["blur", "myCustomEvent"]
add-on-events="addTagOnEvents"
@terohe
Copy link

terohe commented Mar 11, 2014

+1 I was also looking for such a feature.

@mbenford
Copy link
Owner

That seems a nice feature to have. I'll think more about it. Thanks for the suggestion! 👍

@OrelKix
Copy link

OrelKix commented Dec 25, 2014

Hey, any news about this feature?
It would be very helpful.

@AlexanderKozhevin
Copy link

Well, this is quite important feature.

@mbenford
Copy link
Owner

This issue was selected to be spring-cleaned by a script. More information can be found here.

If anyone thinks this was a mistake and this issue should be reopened, please leave a message below explaining why. Before doing so, please consider reading the CONTRIBUTING file.

@otothem
Copy link

otothem commented Apr 25, 2017

I'd like this feature to be reopened simply because it would make the directive more flexible and usable. For example, my project requires semicolon as a delimiter. It seems I'm not alone in this situation, judging from other issues.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants