Recommend an extension to use #203
Comments
|
Based on this conversation:
I am assuming it is |
|
What would be the downside to shortening the extension to just .gql? |
|
For one, it is used by another software http://filext.com/file-extension/GQL. Albeit, it seem to no longer be an active use.
|
|
We use |
|
For the record, |
|
Is this still being developed? Most example projects and articles still use |
|
I’m happy to entertain a formal RFC to add errata to the spec to explain
that .graphql is the preferred extension when saving files in the graphql
language.
Of course .js should only be used for JavaScript files
On Fri, Jul 19, 2019 at 9:46 AM Indrek Lasn ***@***.***> wrote:
Is this still being developed? Most example projects and articles still
use .js. Which one is the correct way?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#203?email_source=notifications&email_token=AAAMHUVOUQW7YHZG23EYPYLQAHVX7A5CNFSM4CNHUZE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ME6OI#issuecomment-513298233>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAMHUUMZ65XRVFLAQNWBO3QAHVX7ANCNFSM4CNHUZEQ>
.
--
Lee Byron
|
|
I'm confused by the apparent implicit consensus to use |
|
These are two parts of one GraphQL language. The same situation with SQL: Data Manupulation Language (DML) and Data Definition Language (DDL) - both have |
…ed upon, file extension (`.graphql`, see graphql/graphql-spec#203 (comment)).
I looked into the various configuration files we currently have checked in, after reading the issue (#86) that was opened on whether or we should have any editor specific files in the repository. I noticed we check in some files that are not used by anyone, a file that is likely only used by me (and only rarely tbh), and some that we can move to to a designated folder, to reduce some of the clutter without affecting editor functionality. This PR brings the repo to a state where the only editor specific files are contained in `.idea`. As we discuss the issue mentioned above, we might end up removing this folder all together, but I'd like us to make that decision against this PRs version of the repository (cleaner, less cluttered, reflects one of the suggestions in the issue) Commits: * _Move_ all IntelliJ config files to `.idea` * _Delete_ `cli/.graphqlconfig` -- this doesn't need to be checked in to make anyone more productive in a significant or commonly used way (i.e. this is only for IJ users with a specific plugin and can easily be created locally. I've added it to .gitignore). * _Delete_ config files that we don't use (`.travis.yml`, `bulk.yaml`, `vagga.yaml`) that were copied over when we forked `graphql-parser`. * _Rename_ the `github.gql` file to use the more common, seemingly agreed upon, file extension (`.graphql`, see graphql/graphql-spec#203 (comment)).
Let me correct you. It is not natively recognised, but there is an extension for GraphQL language which enables recognition of graphql files. At least that's the case for PHPStorm which is the same platform. |
There is no official recommendation for what file extension to use to store GraphQL schemas/ queries. I am assuming it would be either
.graphqlor.gql.Making an official recommendation would increase consistency across all projects.
The text was updated successfully, but these errors were encountered: