Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console warnings in latest gatsby version due to Styled component #947

Closed
ehowey opened this issue May 22, 2020 · 4 comments
Closed

Console warnings in latest gatsby version due to Styled component #947

ehowey opened this issue May 22, 2020 · 4 comments

Comments

@ehowey
Copy link

ehowey commented May 22, 2020

Describe the bug
Since updating to the latest version of Gatsby I am seeing a bunch of console warnings that look like this:

warn ESLintError: 
/Users/erichowey/Coding/erichoweydev/src/components/work-card.js
  44:9  warning  Imported JSX component h4 must be in PascalCase or SCREAMING_SNAKE_CASE  react/jsx-pascal-case
  45:9  warning  Imported JSX component p must be in PascalCase or SCREAMING_SNAKE_CASE   react/jsx-pascal-case
  48:9  warning  Imported JSX component p must be in PascalCase or SCREAMING_SNAKE_CASE   react/jsx-pascal-case

Basically what is happening is that it doesn't like the <Styled.p> syntax and is complaining. Not a big deal - but maybe worrying for newer users of Theme-UI. Not sure if this would be resolved here or on the Gatsby end so I will cross post it.

@jxnblk
Copy link
Member

jxnblk commented May 22, 2020

Thanks! Since nothing has changed in Theme UI's API and this sounds like a change in a lint rule, I think this would need to be addressed either in Gatsby or upstream

@ehowey
Copy link
Author

ehowey commented May 24, 2020

That is what I figured - more of an annoyance than anything. I will leave this open just in case anyone else comes across the issue. Hopefully resolved on Gatsby's end of things.

@ehowey
Copy link
Author

ehowey commented May 28, 2020

Closed by gatsbyjs/gatsby#24560

@ehowey ehowey closed this as completed May 28, 2020
@Kev-Y-Huang
Copy link

As of gatsby version 2.31.0, this error is back.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants