-
Notifications
You must be signed in to change notification settings - Fork 32
[feature idea] graphql-tag support. #69
Comments
It's unfortunate this issue has gone so long unanswered. I came across the same need to enable template syntax highlighting with the If you take a look at the tests for apollo-fetch, you'll see the use of the So in your case, it would be: import { createApolloFetch } from 'apollo-fetch';
import { print } from 'graphql';
import gql from 'graphql-tag';
const query = gql`
query CurrentUser {
currentUser {
login,
}
}
`
const fetcher = createApolloFetch({ ... });
fetcher({ query: print(query) }).then(...).catch(...); |
Any knowledge on when this might be implemented? Kind of a buzzkill to have to use the |
@codemonkey800 |
I'm curious about the reason why gql is not supported. It caught me completely by surprise, and the absence of |
As mentioned in #80 (and since #193 now also in the main README) this library is deprecated in favor of Is migrating to |
I'm using apollo-fetch in my nodeJS server, to fetch data from my micro services which are also in graphql.
-- works fine. Thank you.
but the thing is that graphql-tag suppose to let us use fragments + let us use plugins which allow auto complete for fields and fragments. (which is EXTREMELY helpful in our huge schemas).
apollo client support it, so I though apollo-fetch would support it too, but I when I try to use apollo-fetch with graphql-tag - I get invalid json response from the microservice. (Java GraphQL).
without graphql - works great, but doesn't let me use very helpful features.
Thank you !
example :
works :
doesn't work :
(Or is the java server responsibility? maybe I need to add him a tool to parse ast ?)
The text was updated successfully, but these errors were encountered: