Description

Backend
Introduced a new operator CHECKLIST, it expects JSON array of objects

[{
 "c": 1,
 "v": "value",
 "d": "desc"
}]

c - checked, used 0, 1 to reduce payload
v - string value
d - description, if not present then it has 0 value to reduce payload

The idea is to filter such array of objects with c == 1 and map values to array with overriding operator to IN.

I wasn't able to determine is value only stored in text format and cached in memory as object instance or it's parsed every time a flag is requested. Also I wasn't able to get any stable performance results on my laptop they fuzzy from time to time, guess this should be done on a dedicated device, possibly I will do that on one of my old (it's even better as sensitive for performance) SBCs. So format is discussible, it could be plain text like 1value,desc\n (first checked, then value until comma[, desc] and \n as element separator) or even base64 encoded binary linked list.

UI
Added new operator type CHECKLIST
Added new (...) buttons on the right of value inputs.

Added edit collection dialog that supports IN, NOTIN, CHECKLIST operators.

Implemented basic validation.
Additional sugar should not be difficult like all check/uncheck, open IN, NOTIN in CHECKLIST mode.

I also want to add that I don’t have significant knowledge of either Golang or Vue, and changes in the code may differ greatly from your expectations 😜

Motivation and Context

Very often you have to work with lists of IDs like GUID or hash that cannot be identified simply by reading. Sometimes there are dozens of them. Sometimes it is necessary to briefly exclude certain elements from the list. All of the above together introduces certain inconveniences when working directly with the JSON representation of the list (array of elements).

How Has This Been Tested?

Backend Unit test + local env.
UI Local environment

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.