Skip to content

POC for an extended record_tags.move#223

Merged
chrisgitiota merged 3 commits intofeat/record-tagsfrom
feat/record-tags-tag-registry
Mar 19, 2026
Merged

POC for an extended record_tags.move#223
chrisgitiota merged 3 commits intofeat/record-tagsfrom
feat/record-tags-tag-registry

Conversation

@chrisgitiota
Copy link
Copy Markdown
Contributor


@chrisgitiota chrisgitiota marked this pull request as ready for review March 19, 2026 09:56
@chrisgitiota chrisgitiota requested a review from itsyaasir March 19, 2026 09:56
/// to track how many records and roles are currently using each tag.
/// Usage counts for roles and tags are summed and build a combined usage count.
public struct TagRegistry has copy, drop, store {
tag_map: VecMap<String, u64>,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't it make more sense to call it registry here ?

Copy link
Copy Markdown
Contributor Author

@chrisgitiota chrisgitiota Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that the field name tag_map is not optimal.

As the field is only used internally IMO a technical and self explanatory name would be good. That said, I would prefer tag_map  over registry because registry is very generic.

BUT: There might be better names than tag_map . Already thought about tags but we have this field name already in the RoleTags

How about using tag_map for now and renaming it later on?

@chrisgitiota chrisgitiota merged commit fafd749 into feat/record-tags Mar 19, 2026
@itsyaasir itsyaasir deleted the feat/record-tags-tag-registry branch April 10, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants