Replies: 2 comments 2 replies
-
(This sounds like a tough one. Needs coordination with |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yeah, this is going to be a tough one. Should we explore the idea of "extensions" to Jotai DevTools? Extensions would allow third-party libraries to customize some behavior and the UI of the DevTools. 🤔 Rough idea import { DevTools } from 'jotai-devtools';
import 'jotai-devtools/styles.css';
+ import { devtoolsExtension } from 'jotai-scope';
const App = () => {
return (
<>
- <DevTools />
+ <DevTools extensions=[devtoolsExtension] />
{/* your app */}
</>
);
}; |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Due to the current implementation of jotai-scope, which creates a copy of an atom regardless of its scope (as shown in this code), duplicated atoms appear in the dev-tool panel when an atom is accessed within multiple scopes.
So I would like to suggest the following enhancements:
ScopeProvider
that they are not scoped in.ScopeProvider
each atom is associated with.Thank you for considering these improvements.
Beta Was this translation helpful? Give feedback.
All reactions