ken-kost
Trying out Ash and LiveView together ![]()
Using latest versions.
I generated a live view using mix ash_phoenix.gen.live and added <.input ... />, everything else is like documented/generated.
But when AshPhoenix.Form.submit(form, params: params) is run it fails, or rather it tries to insert an empty struct. Since I added allow_nil?: false on my attributes it fails. Even though params are correct it’s like they are not transfered to the changeset and an empty changeset is submitted. What could be the issue?
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Latest Ash Threads
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
You’ll need to ensure that the attribute is accepted by the action you are submitting. Try adding
accept [:the_attribute]to the actionken-kost
I have
so
create: :*should accept all params right?edit: I found an example on git, it could help me figure it out. I’ll post update.
zachdaniel
create: :*accepts all public attributes. So if your attribute is not public you will need to explicitly list it. You can do that withcreate: [:*, :thing](as of recent versions)ken-kost
Thanks, that was the issue.
Here’s documentation for reference:
Also a question: Could this be improved (would it make sense), i.e. get an informative error message “fields you are action are not public”?
zachdaniel
Hmm…yeah, so
AshPhoenixpasses theskip_unknown_inputsoption with all of the fields it submits, so that you don’t get errors on unknown inputs. The reason it does this is because often in a form there is “extra data” used to do UI related stuff, and we don’t want that to cause an error. I think adding some kind of warning or error would make sense, but there are some edge cases where you actually can’t do anything about the extra keys in the form, and you wouldn’t be able to clear that warning or error…I’ll have to think about it
clearly a bad DX there, but its one of those things that is more complex than it seems to address (within forms, if you passed these inputs in outside of a form when calling an action, you’d have gotten a clear error message).
ken-kost
So if I understand correctly, too much needed for too little gained.

In short it doesn’t make sense, thanks for clarifying!