Expand description
Structured data a host hands over: a value tree, and a form generated from a description of one.
Neither surface takes a serialization dependency. JsonValue and
Schema are the smallest shapes that express what has to be drawn, and a
host converts into them from whatever crate it already parses with. That
keeps this crate product-neutral in the way SplitLayout already is: the
records are plain, and choosing a format stays the host’s decision.
Both refuse to be quiet about what they cannot show. A value that is withheld reads as withheld rather than as absent, and a schema field the form cannot draw is reported in place of the control rather than dropped.
Re-exports§
pub use json_view::JsonValue;pub use json_view::JsonView;pub use json_view::ValueKind;pub use schema_form::FieldValue;pub use schema_form::NumberBounds;pub use schema_form::Schema;pub use schema_form::SchemaChoice;pub use schema_form::SchemaField;pub use schema_form::SchemaForm;pub use schema_form::SchemaFormEvent;pub use schema_form::SchemaKind;pub use schema_form::UnrenderableField;
Modules§
- json_
view - A structured view of a value a host parsed somewhere else.
- schema_
form - A form generated from a description of the arguments a call takes.