-
Notifications
You must be signed in to change notification settings - Fork 2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use community provided types for graphql-upload (#2844)
* Use community provided types for graphql-upload * Update package-lock.json * Update package-lock.json * Type processFileUploads promise * Use any type to pass server response type check * Any types * Fix package-lock.json * fastify: Switch `req` type to `ServerResponse` rather than `OutgoingMessage`. While currently we use `OutgoingMessage`, it actually seems to be suggested that `ServerResonse` — which is an extension of `OutgoingMessage`: https://github.com/fastify/fastify/blob/master/docs/TypeScript.md#example Helps-to-land: #2844 * hapi: Switch uploads to receive "raw" request and response. The immediately pressing reason is to align on the same types that the `processRequest` method from `graphql-upload` (aliased here as `processFileUploads`) uses. Using the raw types should be fine as `graphql-upload` only binds to the `response` to receive "close"-like `EventEmitter` events, and uses the `request` side for the piping of data, which should be identical to Hapi's abstraction. Helps-to-land: #2844 * Revert "Any types" This reverts commit 829f22a. While this was once necessary, it should no longer be with the changes in 8e49b28 and 7638f64. * Update CHANGELOG.md for #2844.
- Loading branch information
1 parent
d7d3613
commit e6462c8
Showing
7 changed files
with
25 additions
and
42 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters