Storing and uploading files using the JSON API?

The :file type is primarily meant for accepting files over interfaces. You’d add a file as an argument, and then use a change on the action to take that file and do something with it. Like you can move it from the temporary directory it is uploaded to by default when it’s a plug.upload, etc.

Really need to write a more comprehensive guide on dealing with file uploads: AshJsonApi.Plug.Parser — ash_json_api v1.7.0

Thanks for your quick reply, @zachdaniel !

To be honest, I have no idea how I could do it

I need to add the :file type as an attribute and another :string attribute to indicate the path or URL where I store the file?

Do you think it’s possible to use Wafle or any other upload library with custom storage options to manage the uploaded files in ash?

What would be the basic steps to implement the possibility to work with files?

I guess this is not integrated with ash_admin yet isn’t it?

Thanks for your help!

Correct on the admin question, but not yet, but we would like to implement that

You can potentially use Waffle, although not something like WaffleEcto

create :create_user do
  argument :profile_photo, :file
  change fn changeset, _ ->
    Ash.Changeset.before_transaction(changeset, fn changeset, _ ->
      if upload = changeset.arguments[:file] do
         url = <upload to s3>
         Ash.Changeset.force_change_attribute(changeset, :profile_photo_url, url)
      else
         changeset
      end
    end
  end
end

I realized a made a mistake in the title, I meant Json Api.

Correct on the admin question, but not yet, but we would like to implement that

I am very new to Ash, but if you think it’s a good idea, I could try implementing it in the admin.

My main obstacle is unfamiliarity with the contributions workflow, and I probably need some guidance.

It would be a welcome addition I suspect that it will be surprisingly complex but I could be wrong. Ultimately the pattern would be to fork ash_admin and then submit a PR. Everything would be done in the form component when rendering attribute inputs.

Yeah, right. Images and files are definitely a big problem. Although images and files are an integral part of any web project. Fork ash_admin - is just not right. There is still a lack of taxonomy in the ash_admin data tables.