This package renders Mobiledoc documents through calls to a createElement
function, often referred to as h
(for hyperscript) or provided as a global if you are using JSX. This allows embedding Mobiledoc content “natively” as virtual DOM in frameworks like React, preact, or hyperapp.
Alternatively, you can skip the “virtual” step and build DOM directly with a micro-renderer such as ultradom or even convert mobiledocs to arbitrary ASTs by adopting createElement
’s standard (type: (properties: object) => Node, properties: object, ...children: Node[]) => Node
signature for your builder.
npm install mobiledoc-vdom-renderer --save
or
yarn add mobiledoc-vdom-renderer
/* @jsx h */
import Renderer from 'mobiledoc-vdom-renderer'
// render: (mobiledoc: Mobiledoc) => Node[]
const render = Renderer({ createElement: h })
// Instant <Mobiledoc/> Component
export default function Mobiledoc({ mobiledoc }) {
return <div>{render(mobiledoc)}</div>
}
import Renderer, { upgradeMobiledoc } from 'mobiledoc-vdom-renderer'
Renderer: (options: RendererOptions) => RenderFunction
Creates a render function ((mobiledoc: Mobiledoc) => Node[]
) from the supplied options
-
{ createElement: CreateElement, getCardComponent?: ComponentGetter, getAtomComponent?: ComponentGetter, getMarkupComponent?: ComponentGetter = getMarkupComponentDefault }
-
Any compatible function such as
createElement: ( type: string | Component, properties?: object, ...children: Node[] ) => Node
React.createElement
or hyperscripth
-
Function which returns a string (tag name) or component (
getCardComponent: (type: string) => string | Component
(properties: { payload: object }) => Node
) for the given card type (required if rendering a mobiledoc with cards) -
Function which returns a string (tag name) or component (
getAtomComponent: (type: string) => string | Component
(properties: { payload: object }) => Node
) for the given atom type (required if rendering a mobiledoc with atoms) -
Function which returns a string (tag name) or component (
getMarkupComponent: (tagName: string) => string | Component = getMarkupComponentDefault
(attributes: object) => Node
) to override rendering for the given tag name (for instance, to mix in HTML attributes or render a custom component instead)import { getMarkupComponentDefault } from 'mobiledoc-vdom-renderer'
getMarkupComponent
’s default behavior is exported asgetMarkupComponentDefault
, which passes through valid tag names but throws an error for tags not on Mobiledoc’s markup section or markup whitelists; passing through all tag names instead (as intagName => tagName
) allows (non-standard) mobiledocs containing arbitrary tags to be rendered
-
upgradeMobiledoc: (mobiledoc: Mobiledoc | Mobiledoc02x) => Mobiledoc
Upgrades a mobiledoc from any released version to the latest specification (0.3.1
)
import { Mobiledoc, MobiledocTypes } from 'mobiledoc-vdom-renderer'
This package includes complete Typescript definitions describing the Mobiledoc format, which may be imported directly for use with any mobiledoc-related code.
Contributions—including pull requests, bug reports, documentation, and suggestions—are welcome!
The code is written in Typescript in a pure functional style. Opinionated “best practices,” including functional programming, are strictly enforced by linters—it’ll help to use a code editor which supports both as-you-type linting and type-checking.
git clone https://github.com/bustle/mobiledoc-vdom-renderer.git
cd mobiledoc-vdom-renderer/
npm install
-
Watches the filesystem for changes (chokidar-cli) then lints (Typescript, Standard style, functional JS practices) and tests (ava snapshots) each file you touch
-
- Run the linters and all tests and generate a coverage report (nyc)
-
Updates all snapshots; check your
git
diff before committing! - Fixes many linting errors and applies prettier whitespace conventions
- mobiledoc-kit editor toolkit