Fix: dev css modules classnames should include filename #18
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
Add the css module filename to avoid potential dev classname collisions. See: facebook/docusaurus#5034 Docusaurus just merged this behaviour in master. I think this plugin should follow the same behaviour. Also, I personally encounter classname collisions in development.
|
@rlamana Please, press the merge button! It's a 6 bytes addition to fix a critical bug! ❤️ PS tested this branch on my project, I confirm it fixes the bug. |
|
@rlamana THANK YOU! |
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.
Add the css module filename to avoid potential dev classname collisions.
See:
facebook/docusaurus#5034
Docusaurus just merged this behaviour in master.
I think this plugin should follow the same behaviour.
Also, I personally encounter classname collisions in development.