feat(realtime): Expose store and pubsub for easier access #9138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dthyresson
approved these changes
Sep 6, 2023
thedavidprice
pushed a commit
that referenced
this pull request
Sep 8, 2023
**Problem** We want to be able to do things like invalidate the live query store from outside of a full graphql request - so without access to the context which these properties are typically attached to. Eg: Watching a file for changes and then invalidating a query when that file updates. **Changes** 1. Expose the pubsub and liveQueryStore from the realtime package 2. Minor renaming to make the exporting more convenient **Outstanding** 1. We may wish to do a future refactor to prevent inadvertent mutations of these but this does not need to be done right now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We want to be able to do things like invalidate the live query store from outside of a full graphql request - so without access to the context which these properties are typically attached to.
Eg: Watching a file for changes and then invalidating a query when that file updates.
Changes
Outstanding