Skip to content

FAQ

No. MLForm mounts Web Components into any element. Frameworks shows the lifecycle wiring for React, Vue, Angular, and Astro.

Can I use my own components instead of MLForm’s?

Section titled “Can I use my own components instead of MLForm’s?”

Yes, at three depths: replace individual kinds with custom fields and reports, place MLForm’s controls in your own layout with createPrimitiveAdapter, or render everything from the headless view.

Yes. A transport is any async function; call a local model, worker, or WASM module and return envelopes. See Transports.

Yes, when it uses declarative conditions; function conditions cannot be serialized. Validate it with validateSchema before mounting. See Schemas from a backend.

Does MLForm send HTTP requests, retry, or cache?

Section titled “Does MLForm send HTTP requests, retry, or cache?”

No. Your transport owns the protocol. MLForm owns validation, the request it hands to the transport, and how results reach reports.

Yes, with per-backend mappedTo maps. See Multiple backends.

Labels, control text, and schema copy can be translated. The validation messages of built-in kinds are English in this version. See Localization.

Pick a theme and recipe, override tokens, or define your own theme. Start with Themes and recipes.