/** * BylineFieldEditor (Phase 5 of Discussion #1174). * * Purpose-built create/edit dialog for byline custom-field definitions. * Constrains the type select to the five v1 types declared by the * `BylineFieldType` union — narrower than the content-field universe — * and exposes the `translatable` toggle (the storage-split flag) that * the content `FieldEditor` doesn't have. * * Single-step form (not the type-picker → config flow used by * `FieldEditor`): with only five types a ` handleLabelChange(e.target.value)} placeholder={t`Job title`} />
setField("slug", e.target.value)} // The literal slug is an example identifier, not natural-language // copy — translators will typically leave it as-is, but the // AGENTS.md "every user-facing string via Lingui" rule applies // uniformly, so the catalog extractor sees it. placeholder={t`job_title`} disabled={isEdit} /> {isEdit && (

{t`Slugs cannot be changed after the field is created.`}

)}
{/* Type — disabled on edit because the storage column depends on it */}