Release v5.3.0

Feature/global on (#14)

* Global on

Ensures "global on" isn't randomly removed.
This happened because the hack for "on" inside
domponents would hook in "global on" as well, and they
would be turned off upon domponent removal.

* 5.3.0

Release v5.2.0

Feature/path on mount (#13)

* Path on mount by squint

When squinting and element does not have a path,
but parent element has a path - then set the parent
path on the child mounted element.
No test for this.

* 5.2.0

Release v5.1.0

Feature/subpath (#12)

* Re-introduce the subpath hack

Now .> should work again as before.
Hacked together same was a last time.
In the future it might be better to pass a "sub"
hodor down for such special paths.
Problem with this solution (as before) is that it
does _not_ guarantee support in async actions.

* 5.1.0

Release v5.0.1

5.0.1

Release v5.0.0

Feature/classes (#11)

* Move index to domdom

* createData -> Data

Data is (will be) a class - use as such.

* Convert Stower into class

createStower -> new Stower.

* Prepare for new type of Data

No default classes from Data.

* Convert Hodor to class

* Stower -> DomStower class

* Callback -> ListenerCallback

Type changed in latest version of Data.

* Bump version of Data

* Fix lint warnings

* New era

Convert domdom so React and don (previous on) is
separate from data so they can be imported.
Data will now be sent into elements upon mount,
since that is when Hodor will "kick in".

* Fix sort tests

* Child path listeners

* When

when is now removed again.
Using plain switches.
Waiting for TS (and JS) pattern matching to save us all.

* element.on

Create local element-level listeners guaranteed
to be cleaned up upon element unmount.

* Conditional + element.on

* Mount on/off

* Containement (children)

* Or accept anything

* dd-props -> dom-props

* dd-model

Support via onMounted (mounted) with Data.
Could use domOde.on but instead trying data from mount.

* Hodor tests

Fixed by rewriting setup function to a simpler version.
Less "trying to be clever".

* don -> on

Rename don back to on.

* Flat children by decomposition

* New era of on

Re-do the whole React-initialization part agian.
Back to domdom() creating React, and React.createElement
containing Data.
The previous setup worked fine in most cases, but not all.
The new setup will support "detached" on via a hack.

* Move dom-props to dd-props

The other "dom-"-files are DOM-specific, this one
is domdom-specific.

* Move dom-props to dd-props

The other "dom-"-files are DOM-specific, this one
is domdom-specific.

* Convert domdom to class Domdom

The index still behaves the same.

* 5.0.0

Release v4.12.1

Bump lodash from 4.17.15 to 4.17.19 (#10)

* Bump lodash from 4.17.15 to 4.17.19

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19)

Signed-off-by: dependabot[bot] <[email protected]>

* 4.12.1

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Eirik Brandtzæg <[email protected]>

Release v4.12.0

4.12.0

Release v4.11.12

Feature/attributes (#9)

* Remove special properties

parcel@next (2) introduce these special properties to map back to where the element originates.
Neat stuff. Crashes everything.

* Make sure domdom doesn't crash and burn when a attribute is undefined

* 4.11.12

Release v4.11.11

4.11.11

Release v4.11.10

4.11.10