Editable

Fission

Product

▾

Setup

›

›

Editable is a small inline-edit helper.

In read mode it renders a low-emphasis button showing the current value. In edit mode it swaps that out for a TextInput. This is useful for rename-in-place flows such as editable titles, tags, or list item names.

Example

use fission::prelude::*;

let widget: Widget = Editable {
id: Some(WidgetId::explicit("rename_project")),
value: view.state().project_name_draft.clone(),
placeholder: "Untitled project".into(),
is_editing: view.state().renaming_project,
on_change: Some(with_reducer!(ctx, SetProjectNameDraft(String::new()), on_set_project_name_draft)),
on_edit: Some(with_reducer!(ctx, BeginProjectRename, on_begin_project_rename)),
on_submit: Some(finish_project_rename_action),
on_cancel: Some(cancel_project_rename_action),
}
.into();

The usual reducer flow is to keep both the committed value and the draft in state, start editing with on_edit, update the draft with on_change, and only commit when the product decides the edit is complete.

Field table

Field	Type	Meaning	Notes / default behavior
id	Option<WidgetId>	Stable identity for the editing field.	Defaults to None.
value	String	Current displayed or edited text.	Controlled by app state.
placeholder	String	Text shown when value is empty.	Required for a good empty-state experience.
is_editing	bool	Whether the widget is currently in edit mode.	Controlled by app state.
on_change	Option<ActionEnvelope>	Action fired when the text changes in edit mode.	Like TextInput, the runtime replaces the payload with the current String.
on_submit	Option<ActionEnvelope>	Intended submit action.	Present in the struct, but not currently wired by the checked-in implementation.
on_edit	Option<ActionEnvelope>	Action fired when the read-mode button is pressed.	Usually flips is_editing to true.
on_cancel	Option<ActionEnvelope>	Intended cancel action.	Present in the struct, but not currently wired by the checked-in implementation.

Current behavior

The important implementation detail is that only on_edit and on_change are active today. on_submit and on_cancel exist in the public struct, but the checked-in widget does not yet connect them to Enter, Escape, or blur behavior.

That means Editable is best for simple inline editing where your app can commit changes another way, or where changing the text live is enough.

Specific advice

If you need reliable submit-on-Enter or cancel-on-Escape right now, compose a TextInput and a read-mode Button directly so you can wire the exact behavior yourself.

Production checklist

For Editable, review the fields that change behavior before treating the widget as finished: id, value, placeholder, is_editing, on_change, on_submit. The goal is to make the product rule visible in state and actions, not hidden inside ad-hoc construction code.

•

Bind on_change, on_submit, on_edit, on_cancel to explicit reducer actions and test that the reducer handles unavailable, duplicate, or invalid input safely.

•

Set id only when identity must be stable across filtering, reordering, diagnostics, or tests; otherwise let Fission derive identity from structure.

•

Check the semantics tree for the user-facing label or role that makes this widget understandable without relying only on pixels.

•

Add at least one component or harness test that confirms the visible text, semantic role, action dispatch, and layout constraint that matter for this widget in context.

If a screen starts repeating the same Editable setup, extract a named component around this widget. That keeps the reference API small while making product code easier to read and safer for generated code to copy.

TextInput, Button, FormControl, and FocusScope.