Struct FieldCx 

#[non_exhaustive]
pub struct FieldCx<'a> {
    pub name: &'a str,
    pub id: &'a str,
    pub label: &'a str,
    pub value: &'a FieldValue,
    pub required: bool,
    pub opts: &'a ResolvedOptions,
    pub base: &'a str,
    pub i18n: &'a Translator,
}

The resolved per-field state a field type renders from.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

name: &'a str

The submitted/DOM field name (becomes a path with repeaters).

id: &'a str

A DOM-safe id for the control and its label’s for.

label: &'a str

value: &'a FieldValue

required: bool

Derived from the merged (intrinsic + descriptor) rules.

opts: &'a ResolvedOptions

base: &'a str

The admin mount path (e.g. /admin), so a type that calls an endpoint (the reference picker) builds its URL without knowing routing conventions.

i18n: &'a Translator

The request’s translator, for the strings a field type localizes itself.

label above is already localized by the caller, because the framework chrome renders it too. A composite type is the case this exists for: a repeater’s sub-field labels are declared inside the type and never pass through the caller, so without this they could only render from their source string, untranslated on every surface.