mattmartian
How to set a limit for inputs_for? / Frontend only pagination on a changeset form
Hi there!
Within my form changeset there is a field that holds more than 700 records, I would paginate straight from the DB however I need all of them to be in memory, but only 5 to display on the screen. Can anybody help with this or if this is even possible at all? I need to be able to edit the form fields as well. Below is some of my code
FORM
<.form let={f}
for={@ice_cream_changeset}
id="ice-cream-edit-form"
phx-change="validate"
phx-submit="update">
<%= for {rc, index} <- Enum.with_index(inputs_for(f, :ice_cream_schemes, append: [])) do %>
<%= label rc, :cone_type, class: "block text-sm font-medium text-gray-700" %>
<%= select rc, :cone_type, ["Waffle": :waffle, "sugar": :sugar, "regular": :regular], prompt: "Choose Type" %>
<%= label rc, : flavour, class: "block text-sm font-medium text-gray-700" %>
<%= select rc, : flavour, ["vanilla": :vanilla, "strawberry": :strawberry, "chocolate": :chocolate], prompt: "Choose flavour" %>
</.form>
CHANGESET
defmodule IceCream do
@moduledoc """
"""
use Ecto.Schema
import Ecto.Changeset, warn: false
alias Data.Schemas.IceCreamScheme
@primary_key false
embedded_schema do
embeds_many(:ice_cream_schemes, IceCreamScheme)
end
def changeset(schema \\ %__MODULE__{}, params) do
schema
|> cast(params, [])
|> cast_embed(: ice_cream_schemes)
end
end
NESTED CHANGESET
defmodule Data.Schemas.IceCreamScheme do
use Ecto.Schema
import Ecto.Changeset, warn: false
@fields [
:flavour,
:cone_type
]
@primary_key false
embedded_schema do
field(:flavour, :string)
field(:cone_type, :string)
end
def changeset(schema \\ %__MODULE__{}, params) do
schema
|> cast(params, @fields)
|> validate_required(@fields)
end
end
First Post!
LostKobrakai
Why do you need all of them in memory? Are only the items to visible editable or do you need to maintain edits on all items?
0
Last Post!
mattmartian
only the visible items are editable but i need to maintain edits on all items in the event you paginate to page 3 and edit
0
Popular in Questions
I have seen a lot of code which picks the first element from a list using Enum.at(0) instead of List.first. Is there a reason why people ...
New
Lets say I have map like this fetching from my database
%{"_id" => #BSON.ObjectId<58eb1a7a9ad169198c3dXXXX>, "email" => ...
New
I wanted to check elixir version in phoenix because i found that my elixir is 1.5 but when i use Enum.chunk_by it said the function is un...
New
In templates/appointment/index.html.eex:
<%= for appointment <- @appointments do %>
<tr>
<td><%= appoi...
New
I have a phoenix application from which a user can download multiple(5-6) files of size 1MB. I couldn’t find anything related to sending ...
New
As the title describes, I’m trying to run Enum.map() over a list of key/value pairs, where the value is a map. My data looks like this:
...
New
I have a server on AWS, and was running a load test using artillery. When looking at the Phoenix dashboard I see the Ports going to 100% ...
New
Other popular topics
I have seen a lot of code which picks the first element from a list using Enum.at(0) instead of List.first. Is there a reason why people ...
New
I have an umbrella app.
Some of the apps inside depend on other apps in the umbrella, unsurprisingly.
I’m writing a test for one of the...
New
Phoenix 1.4.0 released
Phoenix 1.4 is out! This release ships with exciting new features, most notably
with HTTP2 support, improved deve...
New
I asked this very same question on twitter and got some interesting feedback, but I thought it would be a good question to ask here as we...
New
Hey,
Just curious what are the main benefits of Elixir compared to Clojure?
When is Elixir more useful than Clojure and vice versa?
Th...
New
After calling mix ecto.create I get this error:
17:00:32.162 [error] GenServer #PID<0.412.0> terminating
** (Postgrex.Error) FATAL...
New
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
- #security
- #hex









