This repository has been archived by the owner on Nov 22, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 540
Allow the tag delimiter to be configured explicitly #95
Milestone
Comments
+1 I was also looking for such a feature. |
That seems a nice feature to have. I'll think more about it. Thanks for the suggestion! 👍 |
Hey, any news about this feature? |
Well, this is quite important feature. |
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. |
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.
As of right now, tags can only be created on comma, enter, space, or blur. This can be configured via these attributes:
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:
You could even go as far as allowing the user to specify which events should trigger the code to add a tag.
Example:
That would also allow adding tags on custom user events.
Example:
The text was updated successfully, but these errors were encountered: