Fix valid MiniMessage like <c:#D69F06> being matched by translators#936
Merged
Conversation
R00tB33rMan
approved these changes
Jun 1, 2026
R00tB33rMan
left a comment
R00tB33rMan
left a comment
Member
There was a problem hiding this comment.
Works on prod and doesn't create the same side effects. Approved!
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.
This PR reverts a397bfc, which re-applies #931.
Other than that this PR just bumps
gg.gemstone:componentto1.0.2, which fixes the actual issue, see GemstoneGG/Component#4.