sezaru
I have a component with a textarea input.
I noticed that if the text area has new lines in the start or end of its content and the component is re-rendered, it will remove these new lines.
When looking into the form structure, I noticed these fields:
%Phoenix.HTML.Form{
source: #AshPhoenix.Form<
...
params: %{"male_content" => "\n\nline\n\n"},
source: #Ash.Changeset<
attributes: %{
...
male_content: "line",
...
},
>,
...
params: %{"male_content" => "\n\nline\n\n"},
...
}
As you can see, the params field, both for Phoenix.HTML.Form and AshPhoenix.Form has the new lines correctly, but the Ash.Changeset doesn’t.
I’m guessing that when the re-render happens, the form will replace the textarea content with what is in the Ash.Changeset and remove the new lines.
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #blog-post
- #phoenix_html
- #iex
- #ai
- #graphql
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
sodapopcan
Are you using the textarea from
CoreComponents? The docs call out thatnormalize_valuedoes something around this. I’m not actually sure why this is necessary (of course not saying that it isn’t I just don’t know) and is something I’ve never encountered before. Probably a cross-platform thing? Would love to know myself!sezaru
Just found the issue, seems like strings are trimmed by default in Ash adding the following to the field fixed it:
zachdaniel
Yep! In ecto empty values are implemented at the changeset level Ecto.Changeset — Ecto v3.14.0
But in Ash the action/changeset has no bearing, only the type. It is up to the type whether or not an empty value (like
"") should be transformed intonil. This does mean that additional work may need to be done in the form/action if you want to both allownilvalues but turn empty ("") submissions from a form intonil, but I think generally simplifies things.