Support multipart file uploads through remote schema

Hi, I am having an issue to upload a file via Hasura using the custom resolvers over remote schema as i want to upload a file on the server folder directly and not any third party.

The file upload is working perfectly fine if use the “graphql-yoga” server that is exposed as “remote schema” and even the mutation is added to the Hasura but it give the following error:

{"errors":[{"extensions":{"path":"$","code":"invalid-json"},"message":"invalid json"}]}

Here is how the schema is looking on the Hasura console:

singleUpload(file: Upload!): File!

Here is the code for ‘app.js’ that is entry point of the project:

const server = require("./server");
const path = require("path");
const bodyParser = require("body-parser");

server.start(
  {
    port: process.env.PORT || 4000,
    playground: "/graphql",
    endpoint: "/graphql"
  },
  () => {
    console.log(`The server is running on port: ${server.options.port}`);
  }
);

Here is there server.js file that is referenced in the above app.js:

const GraphQLServer = require("graphql-yoga").GraphQLServer;
const Mutation = require("./src/resolvers/Mutation");

const resolvers = {
  Mutation
};

const server = new GraphQLServer({
  cors: false,
  typeDefs: "./src/schema.graphql",
  resolvers,
  context(request) {
    return {
      request
    };
  }
});
module.exports = server;

Here is the schema that in am using for this:

scalar Upload
type Mutation {
    singleUpload(file: Upload!): File!
}

Here is the Mutation.js:

const fs = require("fs");
const createWriteStream = fs.createWriteStream;

const storeUpload = async ({ stream, filename, request }) => {
  const id = request.userId; // This will just give the current user id
  const path = `files/${id}/${filename}`;
  const dirPath = `files/${id}`;

  fs.mkdir(dirPath, { recursive: true }, err => {
    if (err) {
      throw new Error("File Upload Error.");
    }
  });
  return new Promise((resolve, reject) =>
    stream
      .pipe(createWriteStream(path))
      .on("finish", () => resolve({ id, path }))
      .on("error", reject)
  );
};

const processUpload = async (upload, request) => {
  const { stream, filename, mimetype, encoding } = await upload;
  const { id, path } = await storeUpload({ stream, filename, request });
  return { id, filename, mimetype, encoding, path };
};

module.exports = {
  singleUpload: (obj, { file }, { request }) => {
    return processUpload(file, request);
  }
};

Please let me know if anything else is required.

[sbussard]

Any updates on the ability to upload files through Hasura? Base64 is not an option for one of my use cases

[maaft]

Maybe graphql doesn’t support binary.

Just support the multipart/form-data spec (like everyone else does) and its a done deal.

@vaishnavigvs @shahidhk can we please have an update on this? It should really not be hard to implement (support above mentioned multipart-spec) and would help a lot of users a ton.