Skip to content

Needed changes to use the latest record_tags.move version#228

Open
chrisgitiota wants to merge 2 commits intofeat/record-tagsfrom
feat/record-tags-using-latest-names
Open

Needed changes to use the latest record_tags.move version#228
chrisgitiota wants to merge 2 commits intofeat/record-tagsfrom
feat/record-tags-using-latest-names

Conversation

@chrisgitiota
Copy link
Contributor

@chrisgitiota chrisgitiota commented Mar 19, 2026

This PR provides the needed changes to integrate the latest record_tags.move naming (PR #223) in the other AT Move modules.

The Move sources are compile-able, but some of the tests are failing.

@chrisgitiota chrisgitiota changed the title First part of needed changes to use the latest record_tags.move version WIP: First part of needed changes to use the latest record_tags.move version Mar 20, 2026
@chrisgitiota chrisgitiota changed the title WIP: First part of needed changes to use the latest record_tags.move version Needed changes to use the latest record_tags.move version Mar 20, 2026
@chrisgitiota chrisgitiota marked this pull request as ready for review March 20, 2026 14:05
@chrisgitiota chrisgitiota requested a review from itsyaasir March 20, 2026 14:06

/// Returns if the specified is in use.
/// Returns false if the tag is not contained in the registry.
public(package) fun is_in_use(self: &TagRegistry, tag: &String): bool {
Copy link
Contributor

Choose a reason for hiding this comment

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

is_in_use() is inverted here: it returns true when the usage count is 0, so remove_record_tag() now rejects unused tags and allows deleting tags that are still referenced by roles or records.`

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