fix(v2): theme classic should have lib-next prettified#4274
Merged
Conversation
|
[V1] Deploy preview success Built with commit 8c54004 |
|
Size Change: 0 B Total Size: 544 kB ℹ️ View Unchanged
|
|
Deploy preview for docusaurus-2 ready! Built with commit 8c54004 |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4274--docusaurus-2.netlify.app/classic/ |
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
3 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.
Motivation
./lib-next is the JS you swizzle so it is better for the end user if it's run through prettier during the build process.
Currently, it's not prettified due to the .prettierignore at the root, but it's a mistake