Skip to content
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

Why the schema file is using .graphqls extension? #1047

Closed
rohmanhm opened this issue Feb 19, 2020 · 2 comments
Closed

Why the schema file is using .graphqls extension? #1047

rohmanhm opened this issue Feb 19, 2020 · 2 comments

Comments

@rohmanhm
Copy link

Hi, I'm new to this lib and wondering why do you use .graphqls extension rather than .graphql.

Thanks in advance.

@vektah
Copy link
Collaborator

vektah commented Feb 19, 2020

To differentiate between graphql schema files and graphql query files that often live in the same repo.

AFAIK all tools tools will accept both, but as of 0.11 the default include path is getting a little broader and I don't want to accidentally include graphql queries in the server.

Is this causing an issue?

@rohmanhm
Copy link
Author

Is this causing an issue?

@vektah Nope, it's not caused any issue. I just wondering.

I thought you have some special treatment for a file with extension .graphqls rather than .graphql.

Thanks for the explanation. ❤️

omarkohl added a commit to cleodora-forecasting/cleodora that referenced this issue Dec 1, 2022
Rename the file from schema.graphqls to schema.graphql because it seems
to be a little more common and it's somewhat confusing to have a
different extension. I don't expect we will put query files in the top
level of the repository. See for a discussion:
99designs/gqlgen#1047 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants