Skip to content
Discussion options

You must be logged in to vote

@yudin-s thanks for the reply. After a lot more messing around, I'm now almost certain this behavior is related to the double-rendering that happens in React.StrictMode during development. In production builds, everything works intuitively.

That could be something to note in documentation (some kind of warning that certain edge cases might come up in development that aren't anything to worry about in prod) but I bet not, so I'm closing the discussion for now.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by crymall
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants