Move apollo-graphql package into the apollo-tooling repo

[trevor-scheer]

This is the first step to moving the new apollo-graphql package into this repo, from apollo-server.
The second step will be to PR the removal from apollo-server.

This is almost a wholesale copy/paste. A couple changes worth noting:

• Rename dist -> lib to match the pattern of this repo
• esModuleInterop and target: 'es2016' to match tsconfig of the previous project that it came from

@martijnwalraven pointed out the dependency on node@6 within apollo-server, so I left that as is.

TODO:

• Update CHANGELOG.md* with your change (include reference to issue & this PR)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass

[abernix]

I think this looks almost right, but the apollo-graphql tests aren't running. I fixed that without too much effort (more on that in a moment) but I also thought I'd comment on the technique for the move itself and try to avoid the wholesale copy/paste which, I think, makes it more difficult to validate the gap between the two repositories (i.e. did anything go wrong?)

Since apollo-graphql is a relatively new repository, it was tempting to not preserve its existing Git history, but I think it's a good habit for us to save that information when possible, rather than have you take the forever-git blame for anything which I may have done wrong with the initial implementation of apollo-graphql which this imports! 😉

The steps to do so are relatively straightforward with the right commands, these which assume that both repositories are using packages/* for their members, and might be worth showing here for posterity:

$ cp -R apollo-server apollo-server-BACKUP
$ cd apollo-server-BACKUP
$ git checkout -b just-apollo-graphql master
$ git filter-branch -f --prune-empty --subdirectory-filter packages/apollo-graphql -- --all
$ git clean -dfx # delete things which are leftover.
$ git filter-branch -f --index-filter '
    git ls-files -sz |
    perl -0pe "s{\t}{\tpackages/apollo-graphql/}" |
    GIT_INDEX_FILE=$GIT_INDEX_FILE.new \
        git update-index --clear -z --index-info &&
        mv "$GIT_INDEX_FILE.new" "$GIT_INDEX_FILE"
' HEAD
$ cd ../apollo-tooling
$ git checkout -b abernix/add-apollo-graphql
$ git remote add local ../apollo-server-BACKUP
$ git pull --allow-unrelated-histories local just-apollo-graphql --no-ff
$ # Complete the merge by solving conflicts and merging them! 🎉

Happy to help you grok these if it's interesting to you, but I went ahead and ran them and got things setup on a new branch in this repository: abernix/add-apollo-graphql and then rebased your changes from this PR on top of it.

The great thing about this technique is that it makes the subtle changes you needed to make very clear, as seen here: 3decc83.

Anyhow, as the branch link above shows, I added two other commits to make testing work:

• bf6e3e1
• bee8eaa

I think with those last couple commits then this PR is LGTM.

My long-winded proposition is, if this all looks good to you, would you entertain the idea of me force pushing that branch to this PR? 😸

[abernix]

Refs: apollographql/apollo-server#2316

[abernix]

Sorry, I have no idea why I referred to the above as relatively straightforward. It's obviously not. It was relatively straightforward only because I happened to know it was possible, took very little time to execute, and knew exactly what to reference.

[trevor-scheer]

@abernix thank you as always for the excellent information. Please force push away! We'll shoot for a merge and publish tomorrow (my morning) if you're available. Would love to discuss your technique as well (it's super interesting to me!)

[abernix]

This is ready, as far as I'm concerned!