question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

rename `<RecoilRoot>` to `<RecoilProvider>` for consistency?

See original GitHub issue

Why call it <RecoilRoot> instead of <RecoilProvider>? The “provider” naming scheme comes from React itself, and is the standard used across the entire community. It seems weird to deviate without specifying why.

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:17
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

11reactions
drarmstrcommented, Dec 10, 2020

Interesting suggestion, thank you.

0reactions
JLarkycommented, Dec 30, 2020

@ianstormtaylor - yes, we’d love more feedback. Though, separate issues or DMs would be good to keep this issue focused. Also note our new RFC for the API based on existing feedback.

<strike>you have used the wrong link 😃 should be [RFC](https://github.com/facebookexperimental/Recoil/issues/804) (#804)</strike>

also in jotai this is called just Provider

Read more comments on GitHub >

github_iconTop Results From Across the Web

<RecoilRoot> | Recoil
Provides the context in which atoms have values. Must be an ancestor of any component that uses any Recoil hooks.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found