Expose flag to disable "duplicate atom key" checking / logging, as it was too noisy in environments such as NextJS or some dev environments using Fast Refresh. (#733, #2020, #2046)
Import RecoilEnv from the recoil package, and set RecoilEnv.RECOIL_DUPLICATE_ATOM_KEY_CHECKING_ENABLED = false in code to disable the checking and logging.
We also support process.env.RECOIL_DUPLICATE_ATOM_KEY_CHECKING_ENABLED=false in NodeJS environments such as NextJs
Caution: This disables all checks for duplicate atom keys including legitimate errors, so use with caution!
Workaround for React 18 environments with nested renderers that don't support useSyncExternalStore(). (#2001, #2010)
0.7.5
Fix useRecoilSnapshot() with React's Fast Refresh during development (#1891)
Fix useRecoilSnapshot() and recoil-sync with changed browser behavior starting with Chrome v104 (#1943, #1936)
Cleanup memory leak when using atoms with selector defaults. (#1821, #1840, #1844)
0.7.3
Enable atoms and selectors to be used in family parameters (#1172)
Add parentStoreID_UNSTABLE to atom effects which is the ID of the parent store it cloned from, such as the host <RecoilRoot> store for useRecoilCallback() snapshots. (#1744)
Atom effects can initialize or set atoms to wrapped values (#1681)
Allow async selectors to re-evaluate when async dependencies are discovered with stale state (#1736)
0.7.1
Typing
Add explicit children prop to <RecoilRoot> and useRecoilBridgeAcrossReactRoots_UNSTABLE() for TypeScript for @types/react with React 18 (#1718, #1717, #1726, #1731)
Update typing for family parameters to better support Map, Set, and classes with toJSON(). (#1709, #1703)
Fixes
Avoid dev-mode console error with React 18 when using shared async selectors across multiple <RecoilRoot>'s. (#1712)
Cleanup potential memory leak when using async selectors. (#1714)
Fix potentially hung async selectors when shared across multiple roots that depend on atoms initialized with promises that don't resolve. (#1714)
0.7.0
New Features
The default value is now optional for atom() and atomFamily(). If not provided the atom will initialize to a pending state. (#1639)
Publish RecoilLoadable.loading() factory for making an async Loadable which never resolves. (#1641)
Breaking Changes
Selector's get() and Atom's default can now accept a Loadable to put the node in that state. If you wish to store a Loadable, Promise, or RecoilValue directly you can wrap it with selector.value() or atom.value(). (#1640)
useRecoilCallback() now provides a snapshot for the latest state when the callback is called instead of the latest rendered state, which had issues (#1610, #1604)
Improvements / Optimizations
Automatically retain snapshots for the duration of async callbacks. (#1632)
Optimization for more selector dependencies. 2x improvement with 100 dependencies, 4x with 1,000, and now able to support 10,000+. (#1651, #1515, #914)
Better error reporting when selectors provide inconsistent results (#1696)
Workaround for React 18 environments with nested renderers that don't support useSyncExternalStore() (#2001, #2010)
Expose flag to disable "duplicate atom key" checking / logging, as it was too noisy in environments such as NextJS. (#733, #2020, #2046)
Import RecoilEnv from the recoil package, and set RecoilEnv.RECOIL_DUPLICATE_ATOM_KEY_CHECKING_ENABLED = false in code to disable the checking and logging.
We also support process.env.RECOIL_DUPLICATE_ATOM_KEY_CHECKING_ENABLED=false in NodeJS environments such as NextJs
Caution: This does infact disable all checks for duplicate atom keys, so use with caution!
0.7.5 (2022-08-11)
Fix useRecoilSnapshot() with React's Fast Refresh during development (#1891)
Fix useRecoilSnapshot() and recoil-sync with changed browser behavior starting with Chrome v104 (#1943, #1936)
Cleanup memory leak when using atoms with selector defaults. (#1821, #1840, #1844)
0.7.3 (2022-06-01)
Atom effects can initialize or set atoms to wrapped values (#1681)
Add parentStoreID_UNSTABLE to atom effects which is the ID of the parent store it cloned from, such as the host <RecoilRoot> store for useRecoilCallback() snapshots. (#1744)
Enable atoms and selectors to be used in family parameters (#1740)
Allow async selectors to re-evaluate when async dependencies are discovered with stale state (#1736)
0.7.1 (2022-04-12)
Typing
Add explicit children prop to <RecoilRoot> and useRecoilBridgeAcrossReactRoots_UNSTABLE() for TypeScript for @types/react with React 18 (#1718, #1717, #1726, #1731)
Update typing for family parameters to better support Map, Set, and classes with toJSON(). (#1709, #1703)
Fixes
Avoid dev-mode console error with React 18 when using shared async selectors across multiple <RecoilRoot>'s. (#1712)
Cleanup potential memory leak when using async selectors (#1714)
Fix potentially hung async selectors when shared across multiple roots that depend on atoms initialized with promises that don't resolve (#1714)
0.7 (2022-03-31)
New Features
The default value is now optional for atom() and atomFamily(). If not provided the atom will initialize to a pending state. (#1639)
Publish RecoilLoadable.loading() factory for making an async Loadable which never resolves. (#1641)
Breaking Changes
Selector's get() and Atom's default can now accept a Loadable to put the node in that state.
If you wish to store a Loadable, Promise, or RecoilValue directly you can wrap it with selector.value() or atom.value(). (#1640)
... (truncated)
Commits
b63d22a Bump versions and release notes for Recoil 0.7.6 and Recoil Sync 0.2 (#2056)
fbd1490 Fix Flow/Haste issue with OSS environment (#2057)
1aa713b Fixed typo and renamed to mutableSnapshot (#2047)
6436a29 Add explicit annotations to empty arrays in html
9179472 improve API / naming for runtime env settings, expose through public recoil A...
bccb280 fix tests which breaks in GitHub/OSS CI (#2051)
f1a5072 Expose updateItems in RecoilSync's Listen Interface (#2035)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps recoil from 0.6.1 to 0.7.6.
Release notes
Sourced from recoil's releases.
... (truncated)
Changelog
Sourced from recoil's changelog.
... (truncated)
Commits
b63d22aBump versions and release notes for Recoil 0.7.6 and Recoil Sync 0.2 (#2056)fbd1490Fix Flow/Haste issue with OSS environment (#2057)1aa713bFixed typo and renamed to mutableSnapshot (#2047)6436a29Add explicit annotations to empty arrays in html9179472improve API / naming for runtime env settings, expose through public recoil A...bccb280fix tests which breaks in GitHub/OSS CI (#2051)f1a5072Expose updateItems in RecoilSync's Listen Interface (#2035)3f85ae2add warning if Recoil URL Sync Transit detects unstable 'handlers' prop (#2044)0b8f678Better link to documentation and tutorials in README.md (#2032)59e2fafDeploy 0.188.0 to wwwDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)