Enum Filling 

#[non_exhaustive]
pub enum Filling<'a> {
    Absent,
    Text(&'a mut String),
    On(&'a mut bool),
    Ticked(&'a mut Vec<String>),
    Between {
        lower: &'a mut String,
        upper: &'a mut String,
    },
}

What the field currently holds, borrowed from wherever the app keeps it.

The immediate-mode counterpart of makeover_webview::form::Value, and the place the two renderers are forced apart: there the value is read back out of the DOM after the fact, and here the widget writes through this borrow as it is edited. Same reason the description carries neither.

An enum rather than a bag of options, on the reasoning makeover_webview::form::Value records: a checkbox holding a string is unsayable here, where a struct would let it be said and then have to cope.

#[non_exhaustive] since Ticked arrived, which is the breaking change that made room for it: a host builds these and never matches on them, so the next shape of held value costs nobody a match arm.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Absent

Nothing to edit. The control is drawn and does not answer.

Text(&'a mut String)

The buffer behind anything that takes typed text, a select included: what a select holds is the value of one of its Choices.

On(&'a mut bool)

A checkbox, on or off.

Ticked(&'a mut Vec<String>)

The values of a FieldKind::Checklist’s ticked options.

The values rather than a bool per option, because the options are the description’s and the set is the app’s: a host keeps what was ticked under the option values it submits, and a parallel list of bools would have to be re-aligned with the options every time the list changed. Ticking pushes the option’s value and unticking removes it, so the order is the order things were ticked in, which is no order a handler should read anything into.

Between

The two buffers behind a FieldKind::Interval, lower first.

Two buffers rather than one string with a separator, which is makeover_layout::Field::upper_name’s reason one level down: an interval is submitted under two names, so it is edited as two values, and a delimiter this crate owned could appear inside either of them.

Either end may be empty while the other stands. An open end is an answer – “over 120 BPM” – rather than a half-filled box.

Fields

lower: &'a mut String

The lower end’s buffer.

upper: &'a mut String

The upper end’s buffer.

Trait Implementations

impl<'a> Debug for Filling<'a>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'a> Default for Filling<'a>

fn default() -> Filling<'a>

Returns the “default value” for a type.