"Celebrate the code of the problem domain as opposed to the framework."
merge wires up a view and an optional object representing the application
state and merges it to a selector. Simply put,
merge renders your root view to the DOM.
The first argument to
merge is a string which will be used by
DOMContentLoaded, to find root element. The second argument is the top-level view. This argument is a
Function that returns a function that returns an
HTMLElement such as a
prepare call. The third, optional, argument is an object representing the application's state. This object will passed to the renderer function as an parent argument (i.e. following the view's state if there is one).
Elementree adds a single property to the application's state object. The
route property is a concatenation of
location.hash. Updating the
route property will cause a
history.pushState. Updating the address through browser interations will update the
window object does not exist the call to
merge will return the
outerHTML on the result of the rendering.
-> Function -> HTMLElement
prepare a template function with a state object, creating a view function. At a minimum, a template function is required to be passed as the first argument. The second argument, which is optional, is an object representing the local view state. If the template function is joined with a state, the state object will ALWAYS be the 0th argument to the view function. All parent arguments will follow.
render`template: String` -> HTMLElement
HTMLElement. If the template has more than one root element a
DocumentFragment is returned.
html`unescaped: String` -> HTMLElement
html to interpolate HTML, without escaping it, directly into your template.