Releases: johannschopplich/kirby-headless
Releases · johannschopplich/kirby-headless
v5.0.3
v5.0.2
No significant changes
View changes on GitHub
v5.0.1
v5.0.0
🚀 Features
- Add support for Kirby 5 in resolver methods - by @johannschopplich (ca7dd)
View changes on GitHub
v4.0.2
🐞 Bug Fixes
- Add
AcceptandContent-Typedefault headers back - by @johannschopplich (430b8)
View changes on GitHub
v4.0.1
🐞 Bug Fixes
- Allow
X-Cacheableaccess control header by default - by @johannschopplich (60a33)
View changes on GitHub
v4.0.0
Tip
The plugin now has a proper 📖 documentation!
🚨 Breaking Changes
- Overwrite resolved field values by default - by @johannschopplich (c1c3f)
ℹ️ Migrating from v3 to v4
Kirby Headless v4 contains a breaking change: the result of the toResolvedBlocks() field method has changed. Before, the resolved blocks fields were nested within the resolved key. Now the resolved fields overwrite the original fields. This results in less duplication and a cleaner structure.
Update your frontend code to reflect this change. For example, instead of accessing the resolved key like block.content.resolved?.team, you can now access the resolved field directly like block.content.team.
Resolved Key
If you don't want to update your frontend code, you can still update to v4 and use the old structure by defining a resolvedKey in your config.php:
return [
'blocksResolver' => [
'resolvedKey' => 'resolved'
]
];View changes on GitHub
v3.3.0
🐞 Bug Fixes
- Resolve blocks in
toResolvedLayoutscorrectly - by @johannschopplich (d9416)
View changes on GitHub
v3.2.1
🐞 Bug Fixes
- Rename
overwriteContenttoreplaceValues- by @johannschopplich (4b7d2)
View changes on GitHub
v3.2.0
🚀 Features
overwriteContentoption for resolved blocks - by @johannschopplich (6e5ca)