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
Following a recent discussion about tags, I'm creating one here so that we do not lose any context.
The idea is to no longer rely on tags graph to handle tags in Yeti. There will still be a tags collection to store all existing tags across Yeti but then another model is used to handle tags for all yeti objects.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Following a recent discussion about tags, I'm creating one here so that we do not lose any context.
The idea is to no longer rely on
tagsgraph to handle tags in Yeti. There will still be atagscollection to store all existing tags across Yeti but then another model is used to handle tags for all yeti objects.The
tagscollection would look like this:Then we would have the following model to handle tagged objects
We could even handle the source of the tags:
In order to smoothen the migration, we could also provide a migration script like:
Beta Was this translation helpful? Give feedback.
All reactions