-
Notifications
You must be signed in to change notification settings - Fork 30
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
Use EmptyProvider instead of React.Fragment in Provided #1797
Conversation
Code Climate has analyzed commit ecbb55d and detected 0 issues on this pull request. View more on Code Climate. |
Visit the preview URL for this PR (updated for commit 51441e1): https://co-reality-staging--preview-pr-1797-toyte133.web.app (expires Mon, 19 Jul 2021 12:02:12 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 small fixes (see earlier suggestions) then this should be good to go.
Co-authored-by: Glenn 'devalias' Grant <glenn@devalias.net>
Co-authored-by: Glenn 'devalias' Grant <glenn@devalias.net>
In order not to have console errors in browsers when using
React.Fragment
like in the image,a default no-operation
EmptyProvider
wrapschildren
inProvided