Harrygr

Harrygr

I’m trying to build an upload component to allow uploading of files over graphql. I’m using Absinthe for the server aspect and React + URQL (along with the multipart fetch exchange) for the frontend. I’ve followed the file uploads section of the Absinthe docs and I have it working via curl as follows:

curl -v -X POST -F query="mutation { uploadFile(input: {file: \"myfile\"}) { result }}" -F myfile=@avatar.png localhost:4000/graphql

However I can’t seem to get this same mutation to work when using URQL. The server just responds with a “no query document supplied” error.

Here’s an example of the multipart request from the browser:

-----------------------------283482549016739198714264561499
Content-Disposition: form-data; name="operations"

{"variables":{"input":{"file":null}},"query":"mutation UploadFile($input: UploadFileInput!) {\n  uploadFile(input: $input) {\n    result\n    __typename\n  }\n}\n"}
-----------------------------283482549016739198714264561499
Content-Disposition: form-data; name="map"

{"1":["variables.input.file"]}
-----------------------------283482549016739198714264561499
Content-Disposition: form-data; name="1"; filename="avatar.png"
Content-Type: image/png

‰PNG
 <rest of image data

Could there be a discrepency between implementations?

Showing Posts 1 to 6

benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

Yes, URQL is using a different pattern for file uploads. I’ve been fighting this spec forever because I hate the use of null as a marker for a value that is not null. However it seems this spec is getting popular and this is a fight I’m going to lose eventually. sigh.

Harrygr

Harrygr OP

I see. I agree with your thinking. It seems like URQL itself is pretty modular and I’m using the @urql/exchange-multipart-fetch package (which is part of the core repo) to provide this multipart functionality.

I guess it shouldn’t be too hard to make an Absinthe-specific equivilent.

It would be nice if there was agreement on a standard spec though.

Harrygr

Harrygr OP

There does seem to be a standard for this: GitHub - jaydenseric/graphql-multipart-request-spec: A spec for GraphQL multipart form requests (file uploads). · GitHub. Although I have no idea who has the final say on these things.

In any case, I managed to make a exchange for URQL that uses the pattern adopted by Absinthe.

benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

Yes this is exactly the spec I’m talking about. To be clear, this is the proposed spec by one person. I grant that it has seen increasing adoption within the JS graphql ecosystem, but it is not an official spec by the GraphQL body.

You can read about my specific objects to that spec here: Null means the opposite of Null · Issue #4 · jaydenseric/graphql-multipart-request-spec · GitHub

sb8244

sb8244

Author of Real-Time Phoenix

I found this thread when googling. I didn’t want to rewrite anything on the client because that sounds pretty rough, so I went for the Elixir rewriting approach. I hooked into multipart_to_params, an option to the Plug.Parsers plug that’s usually put in Endpoint

This code works for my simple case locally. I didn’t test with multiple files because that’s not a use case for me. I also didn’t worry about graceful params handling. Use at own risk, but possibly a decent starting point:

defmodule RewriteMultipart do
  def multipart_params(parts, conn) do
    params =
      for {name, _headers, body} <- parts,
          name != nil,
          reduce: %{} do
        acc -> Plug.Conn.Query.decode_pair({name, body}, acc)
      end
​
    params = case params do
      %{"operations" => operations, "map" => map} ->
        map = Jason.decode!(map)
        operations = Jason.decode!(operations)
​
        # Transform the file map to the query variables
        vars =
          Enum.reduce(map, operations["variables"], fn mapping, vars ->
            {name, [path]} = mapping
            path = String.split(path, ".") -- ["variables"]
            put_in(vars, path, name)
          end)
​
        # New query drops operations/map in favor of query/variables
        params
        |> Map.drop(["operations", "map"])
        |> Map.merge(%{"variables" => vars, "query" => operations["query"]})
​
      _ ->
        params
    end
​
    {:ok, params, conn}
  end
end
sescobb27

sescobb27

for posterity, i adapted some solutions into this with some basic tests and a way to do an integration test absinthe integration with apollo's file upload · GitHub

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews