Struct InputsForOptions 

pub struct InputsForOptions {
    pub blank_rows: usize,
    pub add_row_url: Option<String>,
    pub container_id: Option<String>,
}

Options for inputs_for.

Fields

blank_rows: usize

Number of extra blank rows to pre-render after the existing rows. The no-JS fallback lets users fill and submit these without any JavaScript. Defaults to 1; inputs_for always emits at least one blank template row even when this is 0.

add_row_url: Option<String>

Optional htmx URL for the server “Add row” fragment endpoint (see nested_row_fragment). When None, no Add button is rendered and the no-JS path still works via the pre-rendered blank rows.

container_id: Option<String>

Container element id. Defaults to "{collection}-rows".

This id is load-bearing when add_row_url is set: the Add-row button’s hx-target and its hx-vals index scan both select #{container_id}. HTML ids must be unique in a document, so when two or more nested forms for the same child collection appear on one page, each MUST pass a distinct container_id. The {collection}-rows default is correct for a single such form per page; leaving two same-collection forms on the default id produces duplicate ids (invalid HTML) and makes each Add-row button resolve against — and append rows / compute indices from — whichever container the shared id happens to match first, i.e. the wrong form. Distinct ids are the only requirement; any stable, unique string (e.g. "shipping-items-rows" vs "billing-items-rows") works.

Trait Implementations

impl Default for InputsForOptions

Available on crate feature maud only.

fn default() -> Self

Returns the “default value” for a type.