`graphql-config` discussion about graphql-language-service HOT 4 CLOSED

The scope of the .graphqlrc format that we're using at FB goes a bit beyond what's currently defined in graphql-config (app-specific config for multiple apps residing in a single repo, inclusion/exclusion rules etc) but as those are additive changes, it seems possible that the could be added to graphql-config.

I think the other main thing missing is a formal specification for the discovery mechanism for .graphqlrc files (how/where is the file-system traversed, and what are the precedence rules if multiple files are found etc).

from graphql-language-service.

Opened kamilkisiela/graphql-config#16 - I'll close this issue and track the progress there :)

from graphql-language-service.

Thanks a lot for kicking this off @asiandrummer!

One of the main things we've learned at Graphcool, is that our customers prefer configuring a schema endpoint URL instead of downloading and updating a JSON representation of the schema. That's why we've created graphql-config which is also used for babel-plugin-react-relay.

Since we've created this repository quite a few people started to contribute and added support for a graphql-js schema-path or extending the endpoint option by specifying HTTP headers for authentication purposes.

Another interesting source of inspiration is the graphql.config.json file from jimkyndemeyer/js-graphql-intellij-plugin. Maybe @jimkyndemeyer wants to jump in here as well?

from graphql-language-service.

Yeah, graphql.config.json could serve as an inspiration since 8.000+ plugin users already depend on it.

With that in mind, it would be ideal if the user configs could be automatically migrated using a set of JSON transformations.

from graphql-language-service.