This commit is contained in:
@@ -12,6 +12,12 @@ TAG-GROUP - bag of tags
|
||||
Tag groups will become a major way to save filters for things because a lot of filtering will be by tags so this should be a solid feature.
|
||||
- RETRIEVAL / PICKLISTS: need to modify the tag picklist to optionally return TAGGROUP names as well as identify they are group so UI can feature differently
|
||||
|
||||
FILTERING AND SORTING BY TAG-GROUP
|
||||
- All code that filters and sorts by tag should accept a tag group as a separate type of input and dynamically build the tag filter list from the group and individual tags separately
|
||||
rather than storing a list of tags at the moment a group is applied.
|
||||
In this way the filters are always dynamically linked to the tags in the group and reflect the most recent changes to the group
|
||||
tl/dr: don't store the tag id's from a group in the filter, store the group id separately and build the list on query
|
||||
|
||||
FORMAT
|
||||
=-=-=-
|
||||
Copied from stack overflow
|
||||
|
||||
@@ -55,7 +55,11 @@ namespace raven_integration
|
||||
Util.ValidateDataReturnResponseOk(R);
|
||||
|
||||
|
||||
|
||||
//GET PICKLIST OF TAGS FOR GROUP
|
||||
|
||||
//TAG ITEM WITH GROUP OF TAGS
|
||||
|
||||
//UNTAG ALL
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user