evans

@bgentry apologies for the lack of response! Thank you for brining up the issue. James and Sashko are super busy with the React side of things. Looks like we may...

This project is super exciting! I Check out [recast](https://github.com/benjamn/recast). It's an AST parser and it may help you traverse while you do the Flow -> TS conversion.

@nicocrm Thank you for picking this up! Take a look at #364. At least for batching, we will support sending the request only once per batch regardless of the number...

I should have a better answer for you in a couple of hours. The current reasons are simplicity of the middleware and aftwerware in their implementations and clarity of the...

@inxilpro Thank you for the suggestions! Right now, we are going to stick with the current interface for middleware and afterware, so that we get backwards compatibility with Apollo Client's...

#71 fixes the issue with React Native. From our past conversation, we may want to move to the polyfill for 1.0. Though it's looking like we'll deprecate the package. Thank...

@ctavan Thank you for rebasing! I would like to have a lightweight client that is easy to use with middleware for auth. Whether it stays `apollo-fetch` or becomes more link...

@bessey Thanks for openning an issue! I'm curious what you're using the query extraction for? Also as a heads up, we're close to deprecating this package in favor of the...

#67 for reference

An option is to open up the array of functions that create the extensions to receive the same argument as the context creation. Here are the type definitions https://github.com/apollographql/apollo-server/blob/version-2/packages/apollo-server-core/src/types.ts#L56