-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the file to be named .graphqlconfig.json #119
Comments
Use cosmiconfig to achieve this goal easily. |
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, fix kamilkisiela#107, fix kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, fix kamilkisiela#107, fix kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: .graphqlconfig -> .graphqlrc, getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, fix kamilkisiela#107, fix kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: .graphqlconfig -> .graphqlrc, getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, kamilkisiela#107, kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: .graphqlconfig -> .graphqlrc, getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, kamilkisiela#107, kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
Fixed this in #124. Please merge! |
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: .graphqlconfig -> .graphqlrc, getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, kamilkisiela#107, kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: .graphqlconfig -> .graphqlrc, getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, kamilkisiela#107, kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem BREAKING CHANGE: .graphqlconfig -> .graphqlrc, getGraphQLConfig is now async, findGraphQLConfigFile is removed fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, kamilkisiela#107, kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem DEPRECATED: - Use .graphqlrc or other cosmiconfig variations instead of .graphqlconfig[.y[a]ml]. BREAKING CHANGES: - getGraphQLConfig is now async. - findGraphQLConfigFile has been removed. fix kamilkisiela#119, kamilkisiela#116, kamilkisiela#115, kamilkisiela#110, kamilkisiela#109, kamilkisiela#108, kamilkisiela#107, kamilkisiela#99, kamilkisiela#98, kamilkisiela#95, kamilkisiela#93, kamilkisiela#92, kamilkisiela#89
uses smart defaults based on conventional expectations in the JS ecosystem DEPRECATED: - Use .graphqlrc or other cosmiconfig variations instead of .graphqlconfig[.y[a]ml]. BREAKING CHANGES: - getGraphQLConfig is now async. - findGraphQLConfigFile has been removed. fix kamilkisiela#119 fix kamilkisiela#116 fix kamilkisiela#115 fix kamilkisiela#110 fix kamilkisiela#109 fix kamilkisiela#108 fix kamilkisiela#107 fix kamilkisiela#99 fix kamilkisiela#98 fix kamilkisiela#95 fix kamilkisiela#93 fix kamilkisiela#92 fix kamilkisiela#89
Hi there :) We're working on a new version of GraphQL Config. The goal is to make it platform agnostic, flexible enough to use with any tool and framework, reduce the bundle size and a lot more and what's even more important, bring it back to life and keep maintaining. New changes #162 are already merged into master and We decided to use cosmiconfig just like in other libraries we maintain, just like @jedmao did so now you're able to use |
Howdy,
I'm working on tools in the GraphQL ecosystem and like the idea to have a unified configuration file that can be shared by many tools.
Unfortunately, I find the editing experience of the .graphqlconfig file to be a bit unpleasant at the moment.
Issue #52 tracks the idea to provide a JSON schema to allow editors to autocomplete code, which would help a bit. In addition, I want to make the case for allowing the config file to be named
.graphqlconfig.json
:.graphqlconfig.yaml
.graphqlconfig
files would of course still be supported.It is not clear to me if there is any reason why using the json extension for the config file would not be allowed, but I was also unable to find any previous discussion on the issue.
The text was updated successfully, but these errors were encountered: