apollo-federation-file-upload
apollo-federation-file-upload copied to clipboard
File Upload cant upload
I already follow the documentation about this but an error will show
this is the error
please see my source code thank you https://github.com/jaymarkjairi/file-upload
facing same issue, any update on this?
same with version 3.0.0; any updates?
Hello guys. Maybe you both are missing some required setps. Our tests are using apollo v3 and are running fine.
in the example above https://github.com/jaymarkjairi/file-upload, @jaymarkjairi forgot to define the FileUpload resolver. see https://github.com/profusion/apollo-federation-file-upload/blob/master/test/gen-service.ts#L128 Also check: https://www.apollographql.com/docs/apollo-server/data/file-uploads/
We had not yet migrated ApolloServer from apollo-server
to apollo-server-express
; trying that.
Anything else we should look for?
@BenjamenMeyer so this is the case apollo-server
does not bundle the file upload support out of the box. Check the link that I sent (https://www.apollographql.com/docs/apollo-server/data/file-uploads/ )
Quoting the docs: New in Apollo Server 3: Apollo Server 3 does not contain a built-in integration with graphql-upload like in Apollo Server 2. Instead, the instructions below show how to integrate it yourself. You cannot do this with the "batteries-included" apollo-server library; you must use a web framework integration such as apollo-server-express instead. This page shows how to integrate graphql-upload with Express and Fastify. To implement similar functionality with another Node.js HTTP framework (e.g., Koa), see the graphql-upload documentation for more information. Some integrations might need to use graphql-upload's processRequest directly.
Thanks... we're trying to figure out the port to apollo-server-express
@BenjamenMeyer Any updates on this? else we can close this issue.
@oliveirarleo my (now former) employer ended up abandoning the effort and directing all file-uploads through a RESTful API call outside of the Apollo Server Gateway functionality (which we were using to federate a GraphQL API) as we were having too much difficulty getting it to work.
So while we couldn't get it to work, I wouldn't say this issue is closed unless someone else has fixed something, but I'm no longer in a position to contribute to this at all or even validate a fix. Please handle as you feel is appropriate.