sergio

sergio

In Phoenix Liveview uploads, you need to surround the upload helper function in a form, with a submit button.

How can I build something a little more like Github’s experience where you can just upload the image and it gets sent to the server to update the user avatar?

I don’t really care about the dropdown.

Really what I’m looking for is having a button that triggers the file picker dialog, and then automatically submits the form would be a good UX for my usecase.

Any tips?

Showing Posts 1 to 10

c4710n

c4710n

  • Auto uploading can be set by the auto_upload: true option of Phoenix.LiveView.allow_upload/3
  • Auto submitting can be triggered by serveral ways. The one I used is to trigger it in the callback of JS uploader with form.dispatchEvent(new Event("submit", {bubbles: true, cancelable: true}))
sergio

sergio OP

Nice, so using the Uploaders.S3 example from the docs, it looks something like this:

Uploaders.S3 = function (entries, onViewError) {
  console.log(entries);

  entries.forEach((entry) => {
    let formData = new FormData();
    let { url, fields } = entry.meta;
    Object.entries(fields).forEach(([key, val]) => formData.append(key, val));
    formData.append("file", entry.file);
    let xhr = new XMLHttpRequest();
    onViewError(() => xhr.abort());
    xhr.onload = () =>
      xhr.status === 204 ? entry.progress(100) : entry.error();
    xhr.onerror = () => entry.error();
    xhr.upload.addEventListener("progress", (event) => {
      if (event.lengthComputable) {
        let percent = Math.round((event.loaded / event.total) * 100);
        if (percent < 100) {
          entry.progress(percent);
        }
      }
    });

    // Only autosubmit the form if uploading one file.
    if (entries.length == 1) {
      xhr.upload.addEventListener("load", (_event) => {
        const form = entry.fileEl.closest("form");
        form.dispatchEvent(
          new Event("submit", { bubbles: true, cancelable: true })
        );
      });
    }

    xhr.open("POST", url, true);
    xhr.send(formData);
  });
};

Specifically the load event is what we’re looking to attach to. Works great!

c4710n

c4710n

It would be better to check the xhr.status before submitting, because the xhr request may fail.

sergio

sergio OP

According to the docs the load event only happens when the upload completed successfully.

image

c4710n

c4710n

HTTP request returning 2XX code will be considered as success.

Above code is checking the xhr.status === 204 , I simply think the all the load event handlers should consider this condition as success.

munksgaard

munksgaard

If anyone is stumbling over this now, it seems like the official Phoenix documentation has a solution now.

In short, auto_upload: true can be paired with a progress handler which handles the file once it has been completely uploaded:

allow_upload(socket, :avatar, accept: :any, progress: &handle_progress/3, auto_upload: true)

defp handle_progress(:avatar, entry, socket) do
  if entry.done? do
    uploaded_file =
      consume_uploaded_entry(socket, entry, fn %{} = meta ->
        {:ok, ...}
      end)

    {:noreply, put_flash(socket, :info, "file #{uploaded_file.name} uploaded")}
  else
    {:noreply, socket}
  end
end
sergio

sergio OP

Thank you for pointing that out, sweet!

larshei

larshei

Just a small note for anyone who struggles with uploads simply not doing anything:

  1. The live_file_input must be inside a form element
  2. Uploads require phx-change on the form. The handle_event/3 callback does not need to do anything, it may just return {:noreply, socket}.
r4z4

r4z4

This was great and thanks everyone for the help. I do have a follow up, though. Was wondering if anyone has any ideas on how to prevent the phx-change trigger, returning a simple {:noreply, socket}, from performing a refresh and resetting all of my other form inputs. I have the .live_input form below another .simple_form with the idea that the user might fill out some fields, attach an upload, continue filling out the rest of the fields.

Kinda struggling to think of a good way out here. I imagine I could put it in its own LiveView but that seems a little much, since it already appears to be in its own LiveView? I think the “best” solution I have so far is to somehow get the current state of the form at upload and repopulate, but that again seems a little overdone.

Just wondering if I am missing something or if someone out there might have any ideas. Thanks all :slight_smile:

i-n-g-m-a-r

i-n-g-m-a-r

In addition..

Note that the upload will not start when for example the file is larger than max_file_size.
This will not trigger any error or interaction so auto_upload will “fail” silently.
handle_progress/3 will not be called so it might seem like auto upload is not working.

— 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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
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
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
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

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
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews