[#113] Use formatting of existing message component as base#114
Merged
rexlManu merged 1 commit intorexlManu:masterfrom Mar 21, 2026
Merged
[#113] Use formatting of existing message component as base#114rexlManu merged 1 commit intorexlManu:masterfrom
rexlManu merged 1 commit intorexlManu:masterfrom
Conversation
… formatting on top to avoid stripping subcomponent formatting
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.
Implemented a fix to Issue #113
The key is basically to keep using the provided message component and only parse the message to get the configured top-level styling from the FairyChat config.
That way, any subcomponents that might have been formatted or any hover/click events remain in tact, while still applying the configured minimessage formatting.
Let me know if i overlooked something! :)