oliver-kriska/claude-elixir-phoenix / plugins/elixir-phoenix/skills/liveview-patterns
liveview-patterns
VerifiedBuild LiveView: async data (assign_async), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, live_patch. Use when handling interactions, debugging events, or tracking Presence.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/async-streams.md | markdown | 5.6 KB |
| references/channels-presence.md | markdown | 5.1 KB |
| references/components.md | markdown | 2.7 KB |
| references/forms-uploads.md | markdown | 3.3 KB |
| references/js-interop.md | markdown | 8.1 KB |
| references/pubsub-navigation.md | markdown | 4.6 KB |
references/forms-uploads.md
View on GitHub# Forms and Uploads Reference
## Form Handling
```elixir
# Simple form
def mount(_params, _session, socket) do
changeset = Accounts.change_user(%User{})
{:ok, assign(socket, form: to_form(changeset))}
end
def handle_event("validate", %{"user" => params}, socket) do
changeset =
%User{}
|> Accounts.change_user(params)
|> Map.put(:action, :validate) # Triggers error display
{:noreply, assign(socket, form: to_form(changeset))}
end
def handle_event("save", %{"user" => params}, socket) do
case Accounts.create_user(socket.assigns.current_scope, params) do
{:ok, _user} ->
{:noreply,
socket
|> put_flash(:info, "User created")
|> push_navigate(to: ~p"/users")}
{:error, changeset} ->
{:noreply, assign(socket, form: to_form(changeset))}
end
end
# Template
~H"""
<.form for={@form} phx-change="validate" phx-submit="save">
<.input field={@form[:name]} label="Name" />
<.input field={@form[:email]} type="email" label="Email" />
<.button>Save</.button>
</.form>
"""
```
## Debouncing & Throttling
```elixir
# Wait until user stops typing (500ms)
<input phx-debounce="500" />
# On blur only
<input phx-debounce="blur" />
# Rate limit (immediate, then 1x/second)
<button phx-throttle="1000">+</button>
```
## Dynamic Nested Forms
```elixir
# Changeset
|> cast_assoc(:items, sort_param: :items_sort, drop_param: :items_drop)
# Template
~H"""
<.inputs_for :let={item} field={@form[:items]}>
<input type="hidden" name="order[items_sort][]" value={item.index} />
<.input field={item[:name]} label="Item Name" />
<button type="button" name="order[items_drop][]" value={item.index}>
Remove
</button>
</.inputs_for>
<button type="button" name="order[items_sort][]" value="new">
Add Item
</button>
"""
```
## File Uploads
```elixir
def mount(_params, _session, socket) do
{:ok,
socket
|> assign(:uploaded_files, [])
|> allow_upload(:avatar,
accept: ~w(.jpg .jpeg .png),
max_entries: 2,
max_file_size: 8_000_000)}
end
def handle_event("save", _params, socket) do
uploaded_files =
consume_uploaded_entries(socket, :avatar, fn %{path: path}, entry ->
dest = Path.join(["priv", "static", "uploads", entry.client_name])
File.cp!(path, dest)
{:ok, ~p"/uploads/#{entry.client_name}"}
end)
{:noreply, update(socket, :uploaded_files, &(&1 ++ uploaded_files))}
end
# Template
~H"""
<form id="upload-form" phx-submit="save" phx-change="validate">
<.live_file_input upload={@uploads.avatar} />
<%= for entry <- @uploads.avatar.entries do %>
<progress value={entry.progress} max="100">{entry.progress}%</progress>
<%= for err <- upload_errors(@uploads.avatar, entry) do %>
<p class="error">{error_to_string(err)}</p>
<% end %>
<% end %>
<.button type="submit">Upload</.button>
</form>
"""
```
## LiveView 1.0/1.1 Breaking Changes
```elixir
# ❌ REMOVED - phx-feedback-for attribute
# ✅ USE - Phoenix.Component.used_input?/1
errors = if Phoenix.Component.used_input?(field), do: field.errors, else: []
# ❌ REMOVED - live_component/2,3 helper
<%= live_component(FormComponent, id: "form") %>
# ✅ USE - component syntax
<.live_component module={FormComponent} id="form" />
# ❌ REMOVED - push_redirect
# ✅ USE - push_navigate
push_navigate(socket, to: ~p"/path")
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |