alex1
Hello everyone!
I have a question how to make an interval selector. I’m very new to elixir and phoenix and not sure how to solve my problem in the most idiomatic way. Here is what I’m trying to do and it doesn’t work:
<.simple_form id="paste-form" for={@form} phx-change="validate" phx-submit="save">
<.input type="select"
field={@form[:expiration]}
options={["One second", %Postgrex.Interval{secs: 1}]}
/>
...
</.simple_form>
If I do like this, I’ve got
protocol Enumerable not implemented for %{days: 0, microsecs: 0, months: 0, secs: 1} of type Postgrex.Interval (a struct)
So, how should I make an interval selector?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
alex1
I tried to write my own version of CoreComponents.input that would not call
options_for_select, but then I got a different problem: I needed to implement [Phoenix.HTML.Safeprotocol for my interval. What’s worse, from form it was coming as text, so in my context I had parse text and make it back into the interval (EctoInterval).At the end I just made it an integer field
expiration_sec, and that made code so much simpler.Hermanverschooten
You cannot just put complex types into
<option>, put values like1,30,60,300in there and convert them to the correct interval on the backend. Remember that all value-parameters in html are strings.LostKobrakai
Any data you render to html will need to be converted to a string format, which can be placed in the final html. That’s what this protocol is used for. If it’s not implemented then it’s unknown how to convert the value you supplied to that corresponding string/html.
Again that’s how forms in html work. Their inputs have string values and string values are submitted (excluding file uploads). That’s what
Ecto.Type.cast/1callbacks for the ecto type of your field is meant to deal with. Convert from incoming weakly typed formats to stronger typed runtime values. If the ecto type you’re using doesn’t support the string format you need you can wrap it in a custom type you create, which can handle your needed string format and delegate to the underlying ecto type everywhere else.tomciopp
You’re going to want to use iso8601 duration strings to convert to and from
Postgrex.IntervalSo in your html the value for 1 second would be
P1S, etc.