Some templates seems use wrong names
See original GitHub issueGeneral Information
- Bug
Under util.deployTemplates:
const ejsInject = {
componentClassName: component.componentClassName,
componentClassNameKebabCase: paramCase(component.componentClassName),
componentNameCamelCase: component.componentClassName, // <-- this one is not correct
componentStrings: component.componentClassName + 'Strings',
componentPath: component.componentPath,
componentName: component.componentName
};
According to its name, componentNameCamelCase should be initialized with something like camelCase(component.componentName)
SPFx uses camel case component name transformation in scss files, but code above injects componentClassName instead in scss files which is not correct.
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (8 by maintainers)
Top Results From Across the Web
How To Correct Misaligned Label Templates
Last week, we listed five main causes of misaligned label templates. This week, we'll teach you how to fix (and avoid) them for...
Read more >Template:Bad name - Wikimedia Commons
This documentation is transcluded from Template:Bad name/doc. ... You can also simply use the name of the correct category as parameter.
Read more >Wordpress inconsistently parsing "template name: xxx" in ...
Wordpress uses a convention so that files named like page_mytemplatename.php are considered "page templates" and are parsed in order to populate ...
Read more >Something's wrong with your template (bad mojo). The merge ...
If you are using multiple templates in your merge process, merge to each of them separately to find out specifically which template is...
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

Seems to be that it was related to another issue in the past and now it seems to be fixed. If so I will update the templates because of the property of camelCase class name already exists and no extra code is needed.
Thanx for letting me know.
First test on Windows: helloWorld
Second test on Windows: helloworld2
Third test on Windows: Helloworld3
Third test on OSX: Helloworld4
@StfBauer
Helloworld3for you because of OSX?