smon
Recommendations for custom live view upload validation
I am experimenting with live view uploads for the first time, and I was wondering what is the recommended way of doing customized upload validations.
My simple example: I have an interface to upload files to a certain directory, and I want to warn the users of duplicate file names in their upload before they hit the submit button. My consume_uploaded_entries/3 would catch these cases, but I am expecting larger files being uploaded, so some feedback earlier would be nice.
So I could evaluate my uploads assign against a list of existing files by…
… setting :valid to false in the appropriate Phoenix.LiveView.UploadEntry structs.
… generating an appropriate error list for errors in the Phoenix.LiveView.UploadConfig struct.
It feels a little bit like screwing around with Phoenix LiveView implementation internals. Is this the way to do it? Did I miss some kind of helper function?
Marked As Solved
smon
Small update: In order to preserve the errors that got returned by Phoenix’ standard evaluation (size, type, upload count issues), I had to modify the function slightly.
defp mark_duplicate_names(%Phoenix.LiveView.UploadConfig{} = upload, existing_names) do
processed_entries =
upload.entries
|> Enum.map(fn %Phoenix.LiveView.UploadEntry{} =
entry ->
if entry.client_name in existing_names do
Map.put(entry, :valid?, false)
else
entry
end
end)
duplicate_name_errors =
Enum.map(processed_entries, fn %Phoenix.LiveView.UploadEntry{} = entry ->
previous_error? = Enum.any?(upload.errors, fn {ref, _msg} -> ref == entry.ref end)
if entry.valid? or previous_error? do
nil
else
{entry.ref, :name_duplicate}
end
end)
|> Enum.reject(fn val -> is_nil(val) end)
# Combine existing errors with additional ones evaluated here.
errors = upload.errors ++ duplicate_name_errors
upload
|> Map.put(:entries, processed_entries)
|> Map.put(:errors, errors)
end
Popular in Questions
Other popular topics
Latest Phoenix Threads
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security









