Closed rrelmy closed 1 year ago
Sounds like you successfully built the feature you're after using a custom excluder class. Nice!
I don't think this needs to be in the core. You could also consider wrapping the entirety of your single page in a {{ cache }}
tag as an alternative to static caching.
In some projects it would be helpfull to have a inclusion list instead of an exclusion list.
In v3.3 this can be achieved with a custom UrlExcluder class which does some inverted logic., but it would be nice to be able to have such control in the core.
Some ideas we had:
The excluder could support negating But therefor all rules need to be checked instead of stopping after the first.
Have a separate inclusion list That's what we did with a custom class, the structure or naming would need to be improved of course