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
Being able to mark a scratch with either preset or custom tags such as "fake match", "help wanted", etc which are easily viewable from a scratch list and searchable
The text was updated successfully, but these errors were encountered:
How would this articulate ? Some tags would depends on a scratch state, Match override for example would depend on a scratch property, but Help wanted would be a user defined tag.
If a dedicated table is created, let's call it ScratchTag, should we put the state tags in it ? or only the user tags ? Trying to keep the state tag, such as fake match could be difficult, as it could not match at some point.
Do we want to allow any kind of tags, or should we set a preset of values that the user can select from ?
In the system tag I can see Match override and Fork.
I forgot to reply here, but my thought is that scratch tags is an arbitrary mapping of string to scratch. However, the frontend could suggest / decorate common/special ones in unique ways. At the end of the day, though, you could type whatever you want and use it as a way to categorize them
Being able to mark a scratch with either preset or custom tags such as "fake match", "help wanted", etc which are easily viewable from a scratch list and searchable
The text was updated successfully, but these errors were encountered: