refactor(api): implement centralized tag collection #4517
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
heiytor
force-pushed
the
refactor/tag-collections
branch
2 times, most recently
from
c417ddd to
91c3b13
Compare
heiytor
changed the title
heiytor
force-pushed
the
refactor/tag-collections
branch
from
91c3b13 to
ebb731c
Compare
Create a dedicated `tags` collection to centralize tag management across
the application. This replaces the previous string-based tag association
with a reference-based model using tag IDs.
The schema for a tag is as follow:
```json
{
"_id": ObjectId,
"tenant_id": String,
"created_at": Time,
"updated_at": Time,
"name": String
}
```
Update all tag-related collections to use tag IDs instead of tag names.
A migration handles the conversion of existing tag data to the new
format.
API response format now includes tag objects:
```json
{
...
"tags": [
{ "name": String },
{ "name": String },
{ "name": String }
]
}
```
Implement generic tag management methods in the store layer to handle
tag operations (push/pull) consistently across all taggable collections.
Add new query options to filter items by tags.
Introduce dual tag representation in taggable entities:
- TagsID: Internal array of tag IDs (not exposed via API)
- Tags: Array of models.Tag objects for API responses
heiytor
force-pushed
the
refactor/tag-collections
branch
from
ebb731c to
698398a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
partially fixes #4350
Create a dedicated
tagscollection to centralize tag management across the application. This replaces the previous string-based tag association with a reference-based model using tag IDs.The schema for a tag is as follow:
{ "_id": ObjectId, "tenant_id": String, "created_at": Time, "updated_at": Time, "name": String }Update all tag-related collections to use tag IDs instead of tag names. A migration handles the conversion of existing tag data to the new format.
API response format now includes tag objects:
{ ... "tags": [ { "name": String }, { "name": String }, { "name": String } ] }Implement generic tag management methods in the store layer to handle tag operations (push/pull) consistently across all taggable collections. Add new query options to filter items by tags.
Introduce dual tag representation in taggable entities: