How to upgrade to v10?
See original GitHub issueThat snippet doesn’t work anymore: https://github.com/jaydenseric/graphql-upload#class-graphqlupload
In the resolve
method, everything is undefined
:
const { filename, mimetype, createReadStream } = await image
console.log(filename, mimetype, createReadStream)
// undefined undefined undefined
How are we supposed to upgrade from v9?
It looks like image
is now a dedicated class with properties resolve
, reject
, promise
& file
but according to the doc, most of them should only be utilized by processRequest..
Using .promise
seems to solve the issue:
const { filename, mimetype, createReadStream } = await image.promise
But .file
seems to be the resolved promise:
const { filename, mimetype, createReadStream } = image.file
Am I right? Which one is the way to go?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Upgrading subsystems from v10 to v10.0.1.2 on VMware - IBM
Go to the What's New in the latest version information page. Locate the Note: You can access the latest files from <URL link>...
Read more >Upgrading to BigFix Inventory v10 - HCL Product Documentation
For versions 9.2.14 or higher, you can directly upgrade to the latest version. To upgrade to the latest version: Create a backup of...
Read more >Upgrade to v10.8 or later on Azure - CyberArk Docs
Copy the following to your existing machine: · On your existing machine, stop the PrivateArk Database service and run the setup to upgrade...
Read more >The Legendary Umbraco v9 to v10 Upgrade Guide
In terms of the upgrade path, there are a few breaking changes between v9 and v10, however, these changes are minor and are...
Read more >LG V10 Software Update - Verizon
System Update Instructions · Start on the Home screen by tapping the Menu Key · Tap Settings · Tap About Phone · Tap...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Regarding your original issue, it looks like maybe the
GraphQLUpload
scalar is not coming fromgraphql-upload
v10? Or the other way around, perhaps the old middlware/processRequest
is running with the new scalar - could this be because you are Apollo Server?You’re right we used a custom type for the upload and not the one shipped with your lib. Replacing it with
GraphQLUpload
fixed the issue.Thanks for all the explanations and sorry for bothering you about that