persistgraphql
persistgraphql copied to clipboard
apollographql
A build tool for GraphQL projects.
Queries from both external graphql files and JS extraction are not compiled in the same output file
When running a js extraction, it throws a syntax error when there is a commented out query in the code. Ideally it would simply skip over it.
When experimenting with using persisted queries, I found that trying have multiple clients caused potential query ID collisions due to the use of incremental integers as IDs. This adds the...
Graphql can't parse empty documents (e.g. from js files with no `gql` tags); return an empty OutputMap in these cases instead of failing. Example: ```bash # File with no `gql`...
Handle the case when no query document is passed (assuming an error should be thrown). Also enabled `strictNullChecks` to ensure comptibility with this compiler flag. Feel free to provide feeback...
Having a standalone install `persistgraphql` gives a stack dump > Usage: persistgraphql input_file [output_file] (node:46389) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be one of type string, Buffer, or URL....
persistgraphql's serialization always puts fragments at the bottom, whereas apollo-client matches the source. So if you have a query like ``` fragment Y on Z { # etc } query...
First off, let me say thanks for the awesome codebase and toolkit! I am using it with Apollo 2.x now and am really enjoying the lighter network footprint! To help...
Using persisted queries throws and error when using the @connection directive. See https://github.com/apollographql/apollo-client/pull/1801#issuecomment-317625843
Added a transform to remove `@connection` directives while ignoring other directives. Basic tests were also added. This will fix https://github.com/apollographql/persistgraphql/issues/37
