You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the tags field, you cannot at the moment paste a list of comma-separated (or anything-separated) tags. The whole string is parsed as a single tag.
It may be opinionated but I think that tags do not usually contain spaces (or commas, FWIW), and thus the behaviour is rather unusual. When creating, say, an article and inputting tags from another source ('marketing' gave you a list of keywords/tags to put in this article), you want to be able to copy and paste it like you did for the content, the title, or any other field.
If Twill updates its dependency to vue-select > 3.3, it should be possible to add this behavior quite easily by adding a handler to "separate" tags if the value submitted contains a comma (or ; , or a space, or anything — that could be a parameter of the field tag)
This would also allow to tag by entering a comma or a space, which is generally the default behaviour on this kind of field in forms.
Hi
In the tags field, you cannot at the moment paste a list of comma-separated (or anything-separated) tags. The whole string is parsed as a single tag.
It may be opinionated but I think that tags do not usually contain spaces (or commas, FWIW), and thus the behaviour is rather unusual. When creating, say, an article and inputting tags from another source ('marketing' gave you a list of keywords/tags to put in this article), you want to be able to copy and paste it like you did for the content, the title, or any other field.
If Twill updates its dependency to
vue-select
> 3.3, it should be possible to add this behavior quite easily by adding a handler to "separate" tags if the value submitted contains a comma (or;
, or a space, or anything — that could be a parameter of the field tag)This would also allow to tag by entering a comma or a space, which is generally the default behaviour on this kind of field in forms.
See sagalbot/vue-select#971 for reference on the
handlers
method.The changelog between 2.x and 3.x seems quite reasonable : https://vue-select.org/guide/upgrading.html#events-instead-of-callbacks
Would that be something interesting ? Happy to help if needed
Thanks !
The text was updated successfully, but these errors were encountered: