add a first implementation for gathering resource ids #94
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
n1ru4l
force-pushed
the
resource-gathering
branch
from
5b80e75 to
82e2a61
Compare
n1ru4l
commented
Sep 17, 2020
packages/in-memory-live-query-store/src/InMemoryLiveQueryStore.ts
Outdated
Show resolved
Hide resolved
n1ru4l
changed the title
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This PR modifies the
InMemoryLiveQueryStoreto wrap schema resolvers that return a NonNull ID Scalar with a resolver that collects the selected resources for an operation.The
gatherIdfunction could is attached to the passed-incontextValue. However, thecontextValuecan be anything. To workaround that we pass in a new context that wraps the user contextValue. All resolvers are wrapped and will use the correct contextValue for executing the user resolver, while still having access to thegatherIdfunction.The list of resource ids is then merged with the QueryRoot Field coordinates. This allows triggering a query re-execution on a resource basis. E:g.
liveQueryStore.triggerUpdate("Todo:1").