Internal identifiers follow the brand: TreasureBox - #109
Merged
Merged
Conversation
…nt, tb-treasure classes and custom properties
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow-up to #108: the internal identifiers now match the brand vocabulary. The component file is renamed
JewelBox.vue→TreasureBox.vue(git-tracked rename; the import and usage in the homepage update with it), the scoped classestb-jewel-*becometb-treasure-*, and the--tb-jewel-frame-bgcustom property becomes--tb-treasure-frame-bgwith its consumers. No rendered output changes — the classes and variables were renamed together.npm run checkpasses with zero warnings; the repo now contains no occurrence of the word outside this PR description.