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
A feature suggestion: Add Tag with Group - I'm using groups to separate tags (ie letting users select their employment Industry and Expertise and keeping those discreet). I'm using vue-tags-input for the front end. In my save operation I'm passing the data to Laravel and wanting to use retag to save the tags, but there is no retagWithGroup.
I can't use setGroup as I don't have the tags available. If I pull up all the user's tags and setGroup, it would set all their tags to that group, not just those I've just saved... I'm not finding any existing solution for this issue.
The text was updated successfully, but these errors were encountered:
No, we can't override we need to add a new ability
For example, in the case of having a group of "Programmers" and another group of "Accountants", if in the group of "Programmers" there is the label of "failure" that refers to a system error and later in the group From "counters" the same "fault" tag is added, referring to an error in a ledger, it should exist in both groups independently, and should not be rewritten between groups.
What I think is that the "tag_group_id" field must be integrated in the tagging_tagged table to make that difference
Problem with this is what if the tag already exists and already has a group?
A feature suggestion: Add Tag with Group - I'm using groups to separate tags (ie letting users select their employment Industry and Expertise and keeping those discreet). I'm using vue-tags-input for the front end. In my save operation I'm passing the data to Laravel and wanting to use retag to save the tags, but there is no retagWithGroup.
I can't use setGroup as I don't have the tags available. If I pull up all the user's tags and setGroup, it would set all their tags to that group, not just those I've just saved... I'm not finding any existing solution for this issue.
The text was updated successfully, but these errors were encountered: