Declare your React component tree in JSON
npm install react-from-json> Declare your React component tree in JSON
 
react-from-json lets you render React
``jsx`
from JSON
`json`
{
"type": "Foo",
"props": {
"children": {
"type": "Bar",
"props": {
"baz": "Hello, world"
}
}
}
}
It also supports non-recursive structures.
`bash`
npm install --save react-from-json
`jsx
import React from "react";
import ReactFromJSON from "react-from-json";
const entry = {
type: "Foo",
props: {
children: {
type: "Bar",
props: {
baz: "Hello, world",
},
},
},
};
const mapping = {
Foo: ({ children }) => (
const Example = () => {
return
};
`
Props passed to your mapped components include
- propKey - name of the prop that rendered your componentpropIndex
- - index of your component if using flat trees_type
- - the type value for your component...props
- - the resolved value of your props object, with relevant child nodes rendered as components
If your data doesn't follow the type | props shape, react-from-json makes it easy to map your data on the fly using the mapProp prop.
`jsx
import React from "react";
import ReactFromJSON from "react-from-json";
import mapping from "./mapping";
const entryWithDifferentShape = {
_type: "Foo",
children: {
_type: "Bar",
baz: "Hello, world",
},
};
const mapProp = (prop) => {
if (prop._type) {
const { _type, ...props } = prop;
return {
type: _type,
props,
};
}
return prop;
};
const Example = () => {
return (
mapping={mapping}
mapProp={mapProp}
/>
);
};
`
react-from-json also supports flat, non-recursive structures via the special component. This is useful when working with typed systems like GraphQL, and you need to avoid unions.
#### The component
simply maps to another component defined in a components object. If you were using it in React, you would use it like:
`jsx`
which would look up the Button component at index 0 in the components object, resolving to:
`jsx`
For react-from-json we use JSON, so we would write this:
`json`
{
"type": "ComponentLookup",
"props": {
"componentType": "Button",
"componentIndex": 0
}
}
> The id here is set by the componentIndex, since we didn't specify one in the JSON. See this comment on IDs for more information.
#### Example
Here's the same example as above, instead using a for entry.props.baz, and providing a separate components object.
`jsx
import React from "react";
import ReactFromJSON from "react-from-json";
const entry = {
type: "Foo",
props: {
baz: {
type: "ComponentLookup",
props: {
componentIndex: 0,
componentType: "Bar",
},
},
},
};
const mapping = {
Foo: ({ baz }) => (
const components = {
Bar: [
{
type: "Bar",
props: {
baz: "Hello, world",
},
},
],
};
const Example = () => {
return (
);
};
`
react-from-json will map id from the root of your component JSON to the React component's id prop. Likewise, if you specify id under props, it will use this. If you use the component, react-from-json will use the array index as id unless another id is specified. Your id will always take priority.
react-from-json supports generic types for use with TypeScript.
`tsx
import { entry, mapping, components } from "./aboveExample";
import ReactFromJSON from "react-from-json";
interface Components {
Bar: object[];
}
interface Mapping {
Foo: React.ReactNode;
Bar: React.ReactNode;
}
class FooReactFromJSON extends ReactFromJSON
render(): JSX.Element {
return super.render();
}
}
const Example = () => {
return (
);
};
``
MIT © Measured Corporation Ltd