Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Persisted GraphQL Queries
See original GitHub issueIn order to support persisted queries we want to introduce a new abstraction IQueryStorage that represents the query storage.
Queries that are pulled from the query storage should already be validated so that a server does not need to do that when the query is processed.
In order to load the query into the query context we need another middleware that comes first in the pipeline and uses the storage to fetch the query.
https://github.com/apollographql/persistgraphql https://blog.apollographql.com/persisted-graphql-queries-with-apollo-client-119fd7e6bba5 https://facebook.github.io/relay/docs/en/persisted-queries.html
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This one is implemented!
As I’ve been thinking about this more, it feels like implementing persisted queries might benefit from a CQRS design pattern. Specifically breaking the
IQueryStorageinto two interfaces likeIReadStoredQueriesandIWriteStoredQueries(for the dynamic query scenario). I say that because in the static query scenarios, we are really only ever concerned with reading the query from the source and then (likely) maintaining it in memory to rerun on subsequent requests. What are your thoughts on this?