WIP: Allow passing ParseOptions to parse() with GraphQL Language Server#242
WIP: Allow passing ParseOptions to parse() with GraphQL Language Server#242adamjernst wants to merge 1 commit intographql:masterfrom
Conversation
I want to pass some ParseOptions. The obvious way to do this is to specify it in `.graphqlconfig` and make graphql-language-service pick this up and respect it. This is only a start. I haven't figured out the cleanest way to pass this to `GraphQLCache`. That will come next.
|
almost two years later, still more than welcome @adamjernst , otherwise i can take this and run with it with attribution of course! we've migrated this repo since. sorry things got stagnant for a bit. if i dont hear back in a week, I will go ahead and migrate this, as we're trying to migrate out the last from the old repos |
|
Sorry @acao, I forgot about this! Please do run with it! |
|
@adamjernst great thanks will do, this is a solid and important addition to the graphql-config support matrix we have so far. was just summarizing it in an issue i'm about to open in discussion on what we can do with |
3 participants
I want to pass some ParseOptions. The obvious way to do this is to specify it in
.graphqlconfigand make graphql-language-service pick this up and respect it.This is only a start. I haven't figured out the cleanest way to pass this to
GraphQLCache. That will come next.