Release 0.19.7

[johanjanssens]

1. Improve model hash granularity #569

Improved the cache performance and cache granularity by storing required, internal and unique model states in the cache per collection and injecting them back in the model before calculating the hash.

Additionally introduced support for defining custom hash keys for the database and webservice collections. This allows to define how Pages calculates the hash. For example, if a database table contains a modified date, it could be used as the hash key.

Finally, added getHashState() method to the collection model interface to allow to easily specialise how hash states are calculated for custom model collections.

2. Page filters no longer working #571

Fixed a problem with page filters and added support for defining page filters in layouts. These changes give more control over how and when filters can be used. In your layout frontmatter you can now define filters, example

---
layout: default
process:
    filters: [highlight, toc]
---

<ktml:content>

3. Support data:// everywhere in frontmatter

Support for data:// everywhere in the frontmatter for both pages and layouts. You can find more information here: https://github.com/joomlatools/joomlatools-pages/wiki/Data#frontmatter

4. Add ComPagesObjectConfig #573

The objects acts as the base for ComPagesDataObject and is also used in page entity, template helpers and behaviours. Also added get() and has() methods to ComPagesPageObject and ComPagesPageEntity to make it easy to retrieve properties by path.

<?= page()->get('metadata/description') ?>

5. Form redirect to external url #579

External redirects are now supported for forms

6. Throw RuntimeError if collection cannot be found #556

Fixes

• Default page properties not set from extended collections Default page properties not set from extended collections #577
• Do not filter decorated component content Do not filter decorated component content #575
• Model filter state to eager Model filter state to eager #567