Be resilient to Swizzle case typos

[slorber]

🐛 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: #3135
Related test: #3147

[FocalChord]

I will try work on this issue!

[FocalChord]

Any idea why I get this error?

[slorber]

Thanks,

You have this error because of double VV, in addition to weird casing you have an additional letterr

[FocalChord]

Hmm, why does nAVbaR work but not nAVVbAr?

[anshulrgoyal]

@slorber My pr on swizzle should be merged first to avoid conflicts I think

[anshulrgoyal]

This is my pr for swizzle cli #3021

[slorber]

Yes we'll merge it first

Hmm, why does nAVbaR work but not nAVVbAr?

@FocalChord this is expected, there's an additional letter here. You can't swizzle a component that does not exist in the first place, but you should be able to swizzle it if letters are ok but with an incorrect case

[FocalChord]

@slorber Hi, can we get Anshuls pull request merged in please

[slorber]

will try to review it asap, but this bug has higher priority: #3199

[slorber]

merged @FocalChord

[anshulrgoyal]

@FocalChord are u still woking on it?

[FocalChord]

@anshulrgoyal yes

@slorber Hi, as seen in the screenshot below, I get this error now

[slorber]

@FocalChord I merged the PR of @anshulrgoyal that address this issue