You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On gatsby version 2.31.0, I am getting console warnings about PascalCase that was raised in bug number 24327 and seemingly addressed in pull request 24560. At some point, the react/jsx-pascal-case rule was changed and so the fix was reverted in 28689.
The console warnings are different for this bug insofar that <Styled.p> tag raises no errors but <Styled.h1> does where as for the previous bug, it seemed that all Styled components raised warnings.
LekoArts
added
type: upstream
Issues outside of Gatsby's control, caused by dependencies
and removed
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
type: bug
An issue or pull request relating to a bug in Gatsby
labels
Feb 1, 2021
Please report this as a bug at https://github.com/yannickcr/eslint-plugin-react - going forward we'll want this rule to be enabled as it warns against an incorrect pattern (generally speaking) that makes Fast Refresh behave incorrectly. It expects components to be in PascalCase. Although it's unfortunate that the rule has some false positives, this should be fixed upstream instead of us deactivating the rule again.
In the meantime you could set your own ESLint config or deactivate the rule in the individual file. Thanks!
Description
On gatsby version
2.31.0
, I am getting console warnings about PascalCase that was raised in bug number 24327 and seemingly addressed in pull request 24560. At some point, thereact/jsx-pascal-case
rule was changed and so the fix was reverted in 28689.The console warnings are different for this bug insofar that
<Styled.p>
tag raises no errors but<Styled.h1>
does where as for the previous bug, it seemed that all Styled components raised warnings.Steps to reproduce
gatsby develop
Expected result
Should expect no console warnings to occur.
Actual result
Environment
The text was updated successfully, but these errors were encountered: