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

Warning: Prop id did not match.(Server-Client) #372

Closed
canptleon opened this issue May 25, 2023 · 6 comments
Closed

Warning: Prop id did not match.(Server-Client) #372

canptleon opened this issue May 25, 2023 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@canptleon
Copy link

Describe the bug
When I enter the page where I call the Chrono component, a warning comes up in the console.

To Reproduce
Steps to reproduce the behavior:

  1. Go to page
  2. Click on nothing
  3. Scroll down to nothing
  4. See warning at console

Expected behavior
Not getting this warning in console :)

Screenshots
Screenshot 2023-05-25 at 16 01 54

If you need more information, please specify in the comments.
"@emotion/css": "11.5.0",
"@emotion/react": "11.0.0",
"@emotion/server": "11.4.0",
"@emotion/styled": "11.3.0",
"@rebass/grid": "6.1.0",
"react": "^18.2.0",
"next": "^13.1.4",
"react-chrono": "^2.1.2",
"typescript": "4.3.5"

Additional context
Hi, first of all, thank you very much for this library, it's really modern. I got a warning while using it in my nextjs project, do you know the solution? Warning disappears from console when Chrono component is not rendered.

@alexnguyennz
Copy link

I am also getting this with Next.js 13 (app dir and client components) - using react-chrono@2.2.0. For me, the id I get references an empty div (with class TimelineContentRender so I assume it's for something) that is inserted below the main timeline code. Would appreciate any assistance with this.

@prabhuignoto prabhuignoto self-assigned this May 29, 2023
@prabhuignoto prabhuignoto added the bug Something isn't working label May 29, 2023
@prabhuignoto
Copy link
Owner

@alexnguyennz @canptleon do you have a sandbox or a link to the github project where this issue can be reproduced?

@alexnguyennz
Copy link

@paulbfe
Copy link

paulbfe commented Jun 14, 2023

@prabhuignoto I am also getting same error

@prabhuignoto
Copy link
Owner

@paulbfe just wondering if the solutions suggested here work? let me know.

prabhuignoto added a commit that referenced this issue Jun 23, 2023
@prabhuignoto
Copy link
Owner

prabhuignoto commented Jun 23, 2023

alternatively you can now disabled the auto id generation via a new prop noUniqueId as well

https://github.com/prabhuignoto/react-chrono#props

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants