Thank you @jmnda for those links
Sidi_Mohammed
GazeIntoTheAbyss
Is this what you’re looking for?
The options bit are a bit confusing to add if you don’t know how already. I asked someone the other day how to do it and ended up with this.
Add @options with your options in the formcomponent.ex and add :options to the socket.
@options [
{"Newest", "newest"},
{"Oldest", "oldest"},
{"Popular", "popular"},
{"Least Viewed", "least viewed"},
{"Most Popular", "most popular"}
]
@impl true
def update(%{example: example} = assigns, socket) do
changeset = Example.change_example(example)
{:ok,
socket
|> assign(assigns)
|> assign(:changeset, changeset)
|> assign(:options, @options)
}
end
Your inpute type then just needs to be set to “select” and options are obviously the :options in the socket.
:example is whatever your database field is named
<.input field={f[:example]} type="select" options={@options} />
Hope this is what you were after.
edit: No idea why I added so many random popular options lol
1
Sidi_Mohammed
Thank you @GazeIntoTheAbyss, this is so helpful, I understand the idea, that means :example field will be associated with multiple values in handle_event/3 which are selected by the user
0
Sidi_Mohammed
Just last thing, as @codeanpeace has suggested, IO.inspect/1 is required to see what was happening behind scenes because we can’t make any expectation about, for example the Component Function implementation for both <.input field = {@form[:username]} type = "text"> and <.input field = {@form[:username]} type = "radio"> is here but for text we will find user’s entry in handle_event("submit", %{"user" => %{"username" => username....) but for radio we will find it in handle_event("submit", %{"user" => params, "name_of_radio_button" => username}....).
This behaviour shows that a radio button will not be treated as form’s field, so I have to handle errors manually, for example if we want to force the user to select one value from all radio buttons and if he didn’ t an error shows : “you must select a username”, how we can do that ?
0
codeanpeace
Without prepending the . in <.input>, you won’t actually be calling the input/1 function in your core components that appropriately nests the input field within the form.
https://github.com/phoenixframework/phoenix/blob/f8c0ad26ee031ee87a6e7307f6dc1f7722134dd5/installer/templates/phx_web/components/core_components.ex#L264-L271
0
Sidi_Mohammed
@codeanpeace, Iam sorry it was just a written mistake, of course I have used <.input> not <input>.
now I just want to know how to show errors manually for an <.input> which will not be handled as form’s field
0