Generate Rust struct definitions with serde derives from JSON data with Option types for nullable fields.
JSON object members are recast as Rust fields, with nested objects producing additional struct definitions and arrays producing collection fields. The observed strings, numbers, booleans, arrays, objects, and nullability guide the selected Rust types. The declarations include Serde derive annotations, and nullable fields use Option types. The main surprise is that the result reflects only the pasted sample. A field that is always present and non-null in that sample may still be optional or nullable in other responses, so the generated model is a starting point rather than an API contract.
Each JSON object supplies a candidate Rust struct, and each member supplies a candidate field. Nested objects require additional struct definitions, while arrays become Vec fields using a type inferred from their elements. Strings and booleans have direct Rust counterparts; numbers require a concrete numeric choice. The result describes the values present in the pasted JSON, not every value the source may later send.
When the JSON evidence marks a field as nullable, the declaration uses Option<T> around its inferred Rust type. This lets derived Serde deserialization represent null as None. A null value by itself does not reveal the intended inner T, so inspect such fields carefully. The generated Option models the Rust data shape; it is not proof that the producer formally permits omission or null.
Not necessarily in every crate. The project must provide Serde and make the requested derive macros available, commonly through Serde's derive feature. The surrounding module may also need imports, visibility choices, or adjusted type names. Generated identifiers and numeric types still require review because the JSON sample cannot describe your crate layout or the producer's complete contract.
No. With ordinary Serde-derived deserialization, both a missing Option<T> field and an explicit null normally become None. That loses the distinction between omission and null. During serialization, None is normally written as null unless you add behavior such as #[serde(skip_serializing_if = "Option::is_none")]. Use a different representation if that distinction matters.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.