Be resilient to Swizzle case typos
See original GitHub issue🐛 Bug Report
Swizzling a comp with bad casing lead to a component swizzled with a bad name.
Webpack aliases we use for themes are case-sensitive, so we should either:
- find a way to make webpack aliases not case-sensitive
- never create swizzled comps/folders with wrong case
- reject if user does a case-sensitive typo and suggest it the correct name
I thnk 2 and 3 are simpler options.
In any case I think it’s not a very good idea to create a theme/nAVbAR
folder, even if it’s the case the user used.
Related: https://github.com/facebook/docusaurus/issues/3135 Related test: https://github.com/facebook/docusaurus/pull/3147
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Mistakes Don't Have to Be Setbacks: 3 Ways to Be Resilient
Made a mistake? These research-based tips could help you bounce back.
Read more >What Leaders Get Wrong About Resilience
Resilience is important for all employees, but they shouldn't be left to navigate adversity on their own. Instead, organizations must create ...
Read more >Resilience - American Psychological Association
Resilience is the process and outcome of successfully adapting to difficult or challenging life experiences, especially through mental, emotional, ...
Read more >14 men s basketball programs that could end a March ...
Here are 14 schools that could be notable inclusions in the 2022 NCAA tournament, starting with the potential first-time participants. None of these...
Read more >TCRP A-41 [Completed] - Transportation Research Board
Improving the Resiliency of Transit Systems Threatened by Natural Disasters ... Information for this research will be gathered through targeted case studies ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
will try to review it asap, but this bug has higher priority: https://github.com/facebook/docusaurus/issues/3199
@FocalChord I merged the PR of @anshulrgoyal that address this issue