Associate *.gql files with graphql language in GraphQLProject#740
Merged
jbaxleyiii merged 1 commit intoapollographql:masterfrom Nov 27, 2018
Merged
Associate *.gql files with graphql language in GraphQLProject#740jbaxleyiii merged 1 commit intoapollographql:masterfrom
*.gql files with graphql language in GraphQLProject#740jbaxleyiii merged 1 commit intoapollographql:masterfrom
Conversation
Codegen wasn't working for me with my files ending in ".gql". As my IDE plugin recognizes "*.gql" files as graphql, this is very confusing. I see two possible further improvements: 1. Warn when including a file without language association 2. Fallback to `graphql` language
Contributor
|
@brabeji ah great! Thanks for adding this! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codegen wasn't working for me with my files ending in ".gql". As my IDE plugin recognizes "*.gql" files as graphql, this is very confusing.
I see two possible further improvements:
graphqllanguage