This commit is contained in:
2020-05-15 23:37:26 +00:00
parent 7a7b40ce1e
commit 1debeafbbd
2 changed files with 15 additions and 13 deletions

View File

@@ -1,23 +1,29 @@
PRIORITY - ALWAYS Lowest level stuff first
=-=-=-=-
MASS TAG OPS
BULK TAG OPS
NOTE: separate routes for seperate things just to avoid issues, i.e. dont' conflate two different functions in same route
i.e. search and replace, not search and remove
NOTE: no mass tag op route will work with every object in order for safety, there arent' *that* many objects so safer to have people pick them from a list and if they want they can manually check all types
NOTE: no bulk tag op route will work with every object in order for safety, there arent' *that* many objects so safer to have people pick them from a list and if they want they can manually check all types
note: they can use a datalist to select so no need to add any filtering ability here
todo: SET TAGS ability to mass tag items from list (SERVER AND CLIENT)
route: mass tag by type and id collection
route: mass tag by type and all objects no id specified
todo: SET TAGS ability to bulk tag items from list (SERVER AND CLIENT)
route: bulk tag by type and id collection
parameters=Type, [id], tag
route: bulk tag by type and all objects no id specified
parameters=Type, tag
todo: REPLACE TAGS
route: mass replace one tag with another tag by type and id collection
route: mass repalce one tag with another tag by type and all objects no collection
route: bulk replace one tag with another tag by type and id collection
parameters=Type, [id], oldTag, newTag
route: bulk repalce one tag with another tag by type and all objects no collection
parameters=Type, [id], oldTag, newTag
todo: REMOVE TAGS
route: mass remove specified tag by type and id collection
route: mass remove tag by type and all objects no id specified
route: bulk remove specified tag by type and id collection
parameters=Type, [id], tag
route: bulk remove tag by type and all objects no id specified
parameters=Type, tag
todo: API root controller
build mode and server info should be authorized shoudln't they? Unauthorized people have no need to see that stuff