<commit_before># Morphed

Morphed lets you mimic pure rendering of a DOM node while still letting you use your favourite DOM manipulation library. Each time your `update` callback is invoked it receives a fresh copy of the initial node, allowing you to make your changes from scratch each time. Behind the scenes, [morphdom](https://github.com/patrick-steele-idem/morphdom) is used to perform the minimal set of DOM manipulations between the current state and the new state.

Morphed expects to be running in a Browserify, Webpack or similar environment.

## Basic Usage

jQuery is used here for demonstration purposes but it is not required by Morphed.
```javascript
    var $ = require('jquery');
    var Morphed = require('morphed');

    // get our element and set up some state
    var $module = $('#my-module');
    var counter = 0;

    // set up an instance of Morphed with the DOM node and an update function
    var morphed = new Morphed($module[0], function(node) {
        $('.display', node).text('Count: ' + counter);
    });

    // attach a click handler to an increment button
    $module.on('click', '.increment', function() {
        counter++;
        morphed.update(); // invoke the update
    });
```

## Motivation

Working with DOM manipulation libraries can let state get out of hand very quickly. jQuery and friends make it simple to toggle a class here or add add a few nodes there, but before long it's impossible to separate out the business logic from the UI code. Some frameworks work around this issue by rendering the entire app to a virtual DOM and only updating the real DOM with the differences. This is great for many cases but sometimes you're working with a prerendered element (say, from a CMS) and just want to be able to tweak what's already there.

Morphed attempts to get the best of both worlds by passing a copy of the same initial node to your update function every time it is invoked. You can manipulate this element as required to get it to reflect your application's current state and Morphed will replace the old node with this up to date version. This means that you never need to try and "reverse" a DOM manipulation, you simply don't perform it in your update function. Using morphdom behind the scenes allows Morphed to swap out this new version of the node for the old version with the fewest manipulations possible.

## API

### new Morphed(node, updateFunction, options) : Morphed

The `Morphed` constructor supports the following arguments:

- _node_ (`Node`, required) - The node to be updated on each call to `update`.
- _updateFunction_ (`Function(Node[, state])`, required) - The update function to be invoked on each call to update. The first parameter, `Node`, will be always be the initial node. The second parameter, `state`, is optional and its usage is described in the State API section. All manipulations applied to the passed `Node` will be applied to the DOM.
- _options_ (`Object`, optional) - See below for supported options.

Supported options:

- _morphdom_ (`Object`) - This object gets passed through to morphdom. See the [morphdom API documentation](https://github.com/patrick-steele-idem/morphdom#api) for supported options.
- _ignoreAttribute_ (`String`, default `morphed-ignore`) - Change the attribute used to flag a node to be ignored by morphdom. See the Caveats section for the usage of the parameter.
- _initialState_ (`Object`) - Provide an initial state for use with the State API. See the State API section for details.
- _clone_ (`Boolean`, default `true`) - Set this to false to avoid the overhead of cloning DOM nodes. You must instead return a node from the `updateFunction`. Use this with a templating library to generate elements that don't need to be prerendered in the page's source. The `updateFunction` callback will not be passed a node, the state becomes the first parameter.

### update()

Invokes the `updateFunction` callback with a copy of the initial DOM node and the current state. All manipulations performed on the node will be applied to the DOM using morphdom.

## State API

Morphed provides a simple state API to handle state tracking for you. It is modeled on the React Component State API and will cause an `update` each time a state function is called. You can access the Morphed instance's current state with `.state`.

### setState(state)

Merges the passed state with the current state. This will add any new keys and replace existing keys. Old keys will be kept. Calling this function will trigger an `update`.

- _state_ (`Object`) - The new state to merge into the current state.

### replaceState(state)

Replaces the current state with the passed state. Calling this function will trigger an `update`.

- _state_ (`Object`) - The new state.

## State API Usage

Here is the same example as above using `setState` to track the count.

```javascript
    var $ = require('jquery');
    var Morphed = require('morphed');

    var $module = $('#my-module');

    var morphed = new Morphed($module[0], function(node, state) {
        $('.display', node).text('Count: ' + state.count);
    }, {
        initialState: {
            count: 0
        }
    });

    $module.on('click', '.increment', function() {
        morphed.setState({count: morphed.state.count + 1});
    });
```

## Caveats

Using Morphed isn't without its pitfalls but many of them have simple workarounds.

Depending on the type of DOM manipulations you are making, some cached queries or event handlers may be pointing to nodes that are no longer rendered. The key here is to use event delegation to handle events. In jQuery, this can be achieved using `.on` and attaching the handler to the same node that is passed to Morphed, or one wrapping it. For example:

```javascript
    $myNode = $('#my-node');
    var morphed = new Morphed($myNode[0], function() {...});

    // this could break if the button node is morphed
    $('button', $myNode).on('click', function() {...}));

    // this should continue to work regardless of what happens to the DOM
    $myNode.on('click', 'button', function() {...});
```

Some elements are stateful and will lose their current value if they are rerendered. The most obvious examples of this are form input controls. There are two things you can do here to work around this issue. The first is to add a `change` listener to the input and store the value yourself. This is a common (in fact, required) pattern in React and allows you to simply update the element with the real value on each update callback. If you don't want to add a host of callbacks for your inputs, you can tell Morphed to ignore any manipulations made to a particular element by adding the attribute `morphed-ignore`. Any changes made in the update callback to an element with this attribute will not be reflected in the real DOM. All modifications to this element will need to be performed outside of the Morphed update callback.

Due to the way morphdom works, jQuery animations will no longer work. Most of the time these animations can be replaced with CSS animations triggered by a class change. When you find yourself in a situation where this won't work and absoloutely must use a javascript animation, make sure you ignore the animated node with `morphed-ignore`. Be aware, children of this node will be ignored too.

## Contribute

Pull Requests welcome. Please make sure tests pass with:

    npm test<commit_msg>Fixed up indentation in code samples<commit_after># Morphed

Morphed lets you mimic pure rendering of a DOM node while still letting you use your favourite DOM manipulation library. Each time your `update` callback is invoked it receives a fresh copy of the initial node, allowing you to make your changes from scratch each time. Behind the scenes, [morphdom](https://github.com/patrick-steele-idem/morphdom) is used to perform the minimal set of DOM manipulations between the current state and the new state.

Morphed expects to be running in a Browserify, Webpack or similar environment.

## Basic Usage

jQuery is used here for demonstration purposes but it is not required by Morphed.
```javascript
var $ = require('jquery');
var Morphed = require('morphed');

// get our element and set up some state
var $module = $('#my-module');
var counter = 0;

// set up an instance of Morphed with the DOM node and an update function
var morphed = new Morphed($module[0], function(node) {
    $('.display', node).text('Count: ' + counter);
});

// attach a click handler to an increment button
$module.on('click', '.increment', function() {
    counter++;
    morphed.update(); // invoke the update
});
```

## Motivation

Working with DOM manipulation libraries can let state get out of hand very quickly. jQuery and friends make it simple to toggle a class here or add add a few nodes there, but before long it's impossible to separate out the business logic from the UI code. Some frameworks work around this issue by rendering the entire app to a virtual DOM and only updating the real DOM with the differences. This is great for many cases but sometimes you're working with a prerendered element (say, from a CMS) and just want to be able to tweak what's already there.

Morphed attempts to get the best of both worlds by passing a copy of the same initial node to your update function every time it is invoked. You can manipulate this element as required to get it to reflect your application's current state and Morphed will replace the old node with this up to date version. This means that you never need to try and "reverse" a DOM manipulation, you simply don't perform it in your update function. Using morphdom behind the scenes allows Morphed to swap out this new version of the node for the old version with the fewest manipulations possible.

## API

### new Morphed(node, updateFunction, options) : Morphed

The `Morphed` constructor supports the following arguments:

- _node_ (`Node`, required) - The node to be updated on each call to `update`.
- _updateFunction_ (`Function(Node[, state])`, required) - The update function to be invoked on each call to update. The first parameter, `Node`, will be always be the initial node. The second parameter, `state`, is optional and its usage is described in the State API section. All manipulations applied to the passed `Node` will be applied to the DOM.
- _options_ (`Object`, optional) - See below for supported options.

Supported options:

- _morphdom_ (`Object`) - This object gets passed through to morphdom. See the [morphdom API documentation](https://github.com/patrick-steele-idem/morphdom#api) for supported options.
- _ignoreAttribute_ (`String`, default `morphed-ignore`) - Change the attribute used to flag a node to be ignored by morphdom. See the Caveats section for the usage of the parameter.
- _initialState_ (`Object`) - Provide an initial state for use with the State API. See the State API section for details.
- _clone_ (`Boolean`, default `true`) - Set this to false to avoid the overhead of cloning DOM nodes. You must instead return a node from the `updateFunction`. Use this with a templating library to generate elements that don't need to be prerendered in the page's source. The `updateFunction` callback will not be passed a node, the state becomes the first parameter.

### update()

Invokes the `updateFunction` callback with a copy of the initial DOM node and the current state. All manipulations performed on the node will be applied to the DOM using morphdom.

## State API

Morphed provides a simple state API to handle state tracking for you. It is modeled on the React Component State API and will cause an `update` each time a state function is called. You can access the Morphed instance's current state with `.state`.

### setState(state)

Merges the passed state with the current state. This will add any new keys and replace existing keys. Old keys will be kept. Calling this function will trigger an `update`.

- _state_ (`Object`) - The new state to merge into the current state.

### replaceState(state)

Replaces the current state with the passed state. Calling this function will trigger an `update`.

- _state_ (`Object`) - The new state.

## State API Usage

Here is the same example as above using `setState` to track the count.

```javascript
var $ = require('jquery');
var Morphed = require('morphed');

var $module = $('#my-module');

var morphed = new Morphed($module[0], function(node, state) {
    $('.display', node).text('Count: ' + state.count);
}, {
    initialState: {
        count: 0
    }
});

$module.on('click', '.increment', function() {
    morphed.setState({count: morphed.state.count + 1});
});
```

## Caveats

Using Morphed isn't without its pitfalls but many of them have simple workarounds.

Depending on the type of DOM manipulations you are making, some cached queries or event handlers may be pointing to nodes that are no longer rendered. The key here is to use event delegation to handle events. In jQuery, this can be achieved using `.on` and attaching the handler to the same node that is passed to Morphed, or one wrapping it. For example:

```javascript
$myNode = $('#my-node');
var morphed = new Morphed($myNode[0], function() {...});

// this could break if the button node is morphed
$('button', $myNode).on('click', function() {...}));

// this should continue to work regardless of what happens to the DOM
$myNode.on('click', 'button', function() {...});
```

Some elements are stateful and will lose their current value if they are rerendered. The most obvious examples of this are form input controls. There are two things you can do here to work around this issue. The first is to add a `change` listener to the input and store the value yourself. This is a common (in fact, required) pattern in React and allows you to simply update the element with the real value on each update callback. If you don't want to add a host of callbacks for your inputs, you can tell Morphed to ignore any manipulations made to a particular element by adding the attribute `morphed-ignore`. Any changes made in the update callback to an element with this attribute will not be reflected in the real DOM. All modifications to this element will need to be performed outside of the Morphed update callback.

Due to the way morphdom works, jQuery animations will no longer work. Most of the time these animations can be replaced with CSS animations triggered by a class change. When you find yourself in a situation where this won't work and absoloutely must use a javascript animation, make sure you ignore the animated node with `morphed-ignore`. Be aware, children of this node will be ignored too.

## Contribute

Pull Requests welcome. Please make sure tests pass with:

    npm test
{'fraction_non_alphanumeric': 0.07190828302014789, 'fraction_numerical': 0.0008140560341903534, 'mean_word_length': 4.0764462809917354, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3240696', 'n_tokens_mistral': 3770, 'n_tokens_neox': 3615, 'n_words': 2190}