-
-
Notifications
You must be signed in to change notification settings - Fork 713
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 React context for controlled CommentsProvider values #2760
Conversation
🦋 Changeset detectedLatest commit: c6fffba The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
onCommentUpdate: null, | ||
onCommentDelete: null, | ||
} as CommentsStoreState, | ||
} satisfies CommentsStoreState as CommentsStoreState, |
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.
This combined syntax defers to TypeScript to typecheck the initial values, while also preserving the type information from CommentsStoreState.
Only as
: Disable's TypeScript's ability to detect type errors in the initial value
Only satisfies
: Does not apply the CommentsStoreState type to the resulting expression.
|
||
const storeGetters = useCommentsStore().get; | ||
|
||
// Combine getters from context and store |
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.
If this combination of classic context and jōtai becomes a common pattern in the future, we could add a set of helpers for this.
Description
See changesets.