Reclaim full layout control. Want to dive fast? Check this [complete example here](https://github.com/aularon/rjsf-layout-example-nextjs).
npm install rjsf-layoutReclaim full layout control. Want to dive fast? Check this complete example here.
``sh`
npm install rjsf-layout
`tsx
import Form, { Field } from "rjsf-layout";
The Type System: Typed Fields and Data
The above is enough to conceive any complex layout! But that's only the basic offering. Check the Next.js Example for a fully fledged example, or continue reading to learn how
leverages Typescript to provide more features that makes it easier, cleaner, and safer to create RJSF forms! The sections below explore different features accumulatively.$3
Used in the way below,
Field is a typed field component. Similar to the untyped variant in the first example, it allows you to display fields at any point in the components tree. This version is typed, however, in that it provides typing for the name prop, and other features for nested trees.`tsx
`In addition to having autocomplete for the
prop, non-existing fields show TS errors.$3
Automatically populated, typed, field components.
below is equivalent to .`tsx
`$3
You receive a typed
object. Type is inferred from the incoming schema.`tsx
`$3
Instead of
, you can pick individual variables. These are automatically populated, with proper types, based on your schema!`tsx
`More Goodies
$3
Say you have a boolean
field where you want to have a custom toggle-style checkbox. You can simply do this:`tsx
schema
style={{
color: $done ? "green" : "gray",
}}
>
{$done ? "🗹" : "☐"}
)}
$3
tsx
const schema = {
type: "object",
properties: {
name: {
type: "object",
properties: {
first: { type: "string" },
last: { type: "string" },
},
},
languages: {
type: "array",
items: {
type: "object",
properties: {
language: {
type: "string",
enum: [
"arabic",
"chinese",
"english",
"french",
"russian",
"spanish",
],
},
level: {
type: "number",
enum: [1, 2, 3],
},
},
},
},
},
} as const satisfies JSONSchemaObject;Hello ${$name.first || ""} ${$name.last || ""}. You know ${}
{/ ^ If you do not pass in a nested layout, it will fallback to RJSF default rendering of that field/}
{({ Language, Level, $level }) => (
// Custom array item layout
style={{
backgroundColor:
// $level is typed to be 1 | 2 | 3 | undefined
$level === 1
? "lightgreen"
: $level === 2
? "lightblue"
: "pink",
}}
>
$3
tsx
import { Theme } from "@rjsf/mui"; // Or any other;
`$3
Usually, custom submit buttons are passed in as
of the default RJSF Form implementation. Since we repurpose that to provide layout, you can pass any custom submit button in the submitter prop:`tsx
submitter={
}
>
...
`Background, (Brief) History & Acknowledgement
An earlier private version of this was created for a personal (production stage) project around a year ago (RJSF v4). It was more of an exploration/proof of concept. It helped great deal in expressing complex forms and managing them, and reducing development and maintenance time.
Ever since RJSF v5 was released I intended to rewrite what I have in a more-reusable fashion. I had first working version a few months ago and used it in another personal project, but still wanted to achieve more elaborate features before declaring it public-ready. And here we are!
Last feature I included was typing the data variables. I tried with
's JTDDataType before settling on the excellent json-schema-to-ts`.