Clean up configuration cruft (editor specific, and unused files) #87
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.
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:
.idea
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)..travis.yml
,bulk.yaml
,vagga.yaml
) that were copied over when we forkedgraphql-parser
.github.gql
file to use the more common, seemingly agreed upon, file extension (.graphql
, see Recommend an extension to use graphql/graphql-spec#203 (comment)).