Prevent static class names from getting mangled in build #179
Conversation
This file contains 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
Fixes #178 In certain build setups, we can't use `function.name`, since the function will be mangled/minified, and so to ensure the MuiTiptap classes (like `MuiTiptap-RichTextField-content`) are static and consistent, we have to hard-code the component names as strings.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #178
In certain build setups, we can't use
function.name, since the function will be mangled/minified, and so to ensure the MuiTiptap classes (likeMuiTiptap-RichTextField-content) are static and consistent, we have to hard-code the component names as strings.