Add context parameter to validationDidStart and parsingDidStart

[cliedeman]

Added context to parsingDidStart and validationDidStart. Use case is that I collect tracing information in the context object and context is currently unavailable in these 2 hooks.

I also created interfaces for most of the hook methods so that writing graphql-extensions is easier instead of duplicating all the parameters.

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

[apollo-cla]

@cliedeman: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[abernix]

Just one small nit-picky request, but otherwise I think this looks good!

[abernix]

Thanks for breaking these interfaces out!

Can we be more explicit than *Opts and just call these *Options? Unless there's a pattern here that's being followed that I'm missing?

[cliedeman]

No reason. Updated

[abernix]

Thanks for opening this originally. We've done some pretty extensive overhaul to the request pipeline, and I believe that this should now be available in the lifecycle hooks for new request pipeline (#1795).

We're working on updating the documentation to reflect this and I've changed a couple of the labels/milestones on this PR to reflect that. I'll leave this open for now, but I think you might find that this functionality is more easily accessible as of Apollo Server 2.2.0.

[abernix]

Thanks for opening this originally. Following up on my previous comment, I'm going to close this PR as the context is now available to request pipeline lifecycle events via Apollo Server plugins.

If you haven't already tried using the new plugin hooks, I suggest taking a look at the documentation in #2008 (WIP!). We'll likely be deprecating the graphql-extensions API in the future since the new plugin API should be more versatile and cover more extension points.

Let us know if you run into any problems with it!