- 🇬🇧United Kingdom longwave UK
This feels like a job for a contrib module and not something we should encourage in core.
At the moment it's quite difficult for non-module-developer users to exclude one or more single blocks from caching. Since bigpipe technology made it's way into core and is activated by default, there is a much better performance management behind the scenes of Drupal.
Provide a boolean field at block configuration where caching of the block can be turned on or off. Views GUI could be here a role model.
Easier for non-module-developers to handle block caching - so a much better UX. More comfortable for all other Drupalistas :)
Active
11.0 🔥
block.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This feels like a job for a contrib module and not something we should encourage in core.