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?
Trending in Questions
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
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
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
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
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
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
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming












Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
c4710n
auto_upload: trueoption ofPhoenix.LiveView.allow_upload/3form.dispatchEvent(new Event("submit", {bubbles: true, cancelable: true}))sergio
Nice, so using the
Uploaders.S3example from the docs, it looks something like this:Specifically the
loadevent is what we’re looking to attach to. Works great!c4710n
It would be better to check the
xhr.statusbefore submitting, because the xhr request may fail.sergio
According to the docs the
loadevent only happens when the upload completed successfully.c4710n
HTTP request returning 2XX code will be considered as success.
Above code is checking the
xhr.status === 204, I simply think the all theloadevent handlers should consider this condition as success.munksgaard
If anyone is stumbling over this now, it seems like the official Phoenix documentation has a solution now.
In short,
auto_upload: truecan be paired with a progress handler which handles the file once it has been completely uploaded:sergio
Thank you for pointing that out, sweet!
larshei
Just a small note for anyone who struggles with uploads simply not doing anything:
live_file_inputmust be inside aformelementphx-changeon the form. Thehandle_event/3callback does not need to do anything, it may just return{:noreply, socket}.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-changetrigger, returning a simple{:noreply, socket}, from performing a refresh and resetting all of my other form inputs. I have the.live_inputform below another.simple_formwith 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
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_uploadwill “fail” silently.handle_progress/3will not be called so it might seem like auto upload is not working.