Changes

1.2.1

Patch Changes

c24c4cc: Fixes #60, preventing us from parsing documents that use other namespace prefixes than the ones used in the xsi:type definitions in the binding template.

1.2.0

Minor Changes

e89afa9: Add rudimentary support for content model variations through xsi:type. Check the README for details and #58 for the original issue.

1.1.4

Patch Changes

50f84fc: Fix for a bug causing missing attribute values to be intepreted as empty strings. Workaround for a bug in the version of xmldom we're depending on. See #56.

1.1.3

Patch Changes

1da2d3e: Prevent elements bound to missing objects from being inserted. Fixes #54.

1.1.2

Patch Changes

a9f8aac: Bump xmldom to version 0.6.0

1.1.1

Patch Changes

6828baf: Prevent namespace declarations from getting dropped

1.1.0

Minor Changes

f8ac631: Support for a simpler way to map arrays of non-object values.

Instead of binding as array, we're binding as values. With array, every encounter of the element results in a new object getting added to the array. With values, we're not adding any values yet. However, if inside, we encounter something that is bound to value, it will be added to the array as simple value.

Perhaps this example makes it easier to grasp:
```
const template = parse(
  `<foo><bar c-bind="numbers|values">{{value|integer}}</bar></foo>`
);
const data = template.fromXML(`<foo><bar>1</bar><bar>2</bar></foo>`);
// { numbers: [ 1, 2 ] }
```
Instead of this:
```
const template = parse(
  `<foo><bar c-bind="numbers|array">{{value|integer}}</bar></foo>`
);
const data = template.fromXML(`<foo><bar>1</bar><bar>2</bar></foo>`);
// { numbers: [ { value: 1 }, { value: 2 } ] }
```
Note that we currently consider this feature to be unstable. You can use it, but be advised that the notation might change in the future.

1.0.0

Major Changes

88f9ea8: Drop pattern matching approach causing parsing issues

Before, there used to be a mechanism that would allow you to have the same element multiple times within the same template. Only if there would be an exact match with the elements attributes, it would be considered to be decoded based on whatever the template was suggesting.
```
<foo>
  <bar a="1">{first}</bar>
  <bar a="2">{second}</bar>
</foo>
```
Given this template and a file like this:
```
<foo>
  <bar a="2">yay</bar>
</foo>
```
… the resulting data object would be this:
```
{
  "second": "yay"
}
```
It turned out that this was actually causing parsing issues in case the XML serializer decided to introduce namespaces on an element that didn't have a namespace before. Since the mechanism was never in use — as far as I can tell — I decided to drop it.

0.5.3

Fixing a bug that somehow reappeared.

0.5.2

Add type definitions.

0.4.4

Fixes an issue where container elements were getting inserted to aggressively in case of captures.

0.4.3

Fixes a pattern matching bug causing some issues with namespaces. Note that this is related to an undocumented feature which might be dropped in a future major version.

0.4.2

Fixes a bug where bindings on attributes are ignoring specific value types set on those attributes.

0.4.1

Fix a number of issues with RelaxNG generation and namespaces.

0.4.0

Add support for capturing an entire nodeset.
Produce sensible RelaxNG grammars for captures.

0.3.5

Fix a RelaxNG generation issue.

0.3.4

Add CDATA support.

0.3.3

Fixes a bug related to raw data.

0.3.2

Have the ability to get the raw data, even if the fields have been annotated with type annotations.

0.3.1

Fixes a RelaxNG generation bug caused by comment binding

0.3.0

Comments used to offer a way to add more binding instructions to the template. That has now been replaced by the use of processing instructions.
As a result, you can now bind comments to variables:

0.2.0

Dropped preserveWhitespace, contemplating xml:space
Add the posibility to generate RelaxNG schemas from the template

0.1.6

FIX: Falsy values were getting excluded from the output

0.1.5

Upgrade xmldom dependency to ^0.3.0

0.1.4

Added the preserveWhitespace option to do exactly that: preserve whitespace.

0.1.2

Exposed the local name of the root element on the template.