Skip to content

Commit de54257

Browse files
author
Etienne Laurent
committed
improve changelog entry
1 parent 8f4806f commit de54257

File tree

2 files changed

+7
-1
lines changed

2 files changed

+7
-1
lines changed

.editorconfig

+3
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,6 @@ indent_size = 2
99
indent_style = space
1010
insert_final_newline = true
1111
trim_trailing_whitespace = true
12+
13+
[*.md]
14+
trim_trailing_whitespace = false

CHANGELOG.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,10 @@
2222
* Adds possibility for modules to [add extra frontend bundles for scss and js](https://v3.docs.apostrophecms.org/guide/webpack.html). This is useful when the `ui/src` build would otherwise be very large due to code used on rarely accessed pages.
2323
* Loads the right bundles on the right pages depending on the page template and the loaded widgets. Logged-in users have all the bundles on every page, because they might introduce widgets at any time.
2424
* Fixes deprecation warnings displayed after running `npm install`, for dependencies that are directly included by this package.
25-
* Implement custom ETags emission. It allows caching of pages and pieces, using a cache invalidation mechanism that takes into account related (and reverse related) documents updates, thanks to backlinks mentioned above. For now, only single pages and pieces benefit from the ETags caching system (pages' and pieces' `getOne` REST API route, and regular served pages).
25+
* Implement custom ETags emission when `etags` cache option is enabled. [See the documentation for more information](https://v3.docs.apostrophecms.org/guide/caching.html).
26+
It allows caching of pages and pieces, using a cache invalidation mechanism that takes into account related (and reverse related) document updates, thanks to backlinks mentioned above.
27+
Note that for now, only single pages and pieces benefit from the ETags caching system (pages' and pieces' `getOne` REST API route, and regular served pages).
28+
The cache of an index page corresponding to the type of a piece that was just saved will automatically be invalidated. However, please consider that it won't be effective when a related piece is saved, therefore the cache will automatically be invalidated _after_ the cache lifetime set in `maxAge` cache option.
2629

2730
### Fixes
2831

0 commit comments

Comments
 (0)