Hi! Thank you for the suggestion and for sharing the details about the proposed action hook.
Before we consider adding do_action( 'breeze_advanced_cache_file_updated' );, could you please share the complete scenario or use case where you intend to use this hook? It would be helpful to understand what functionality you’re trying to achieve after the advanced-cache.php file is written or deleted, and how this hook would be consumed in practice.
Having a clearer picture of the real-world implementation will allow us to better evaluate the requirement and ensure that any addition aligns well with Breeze’s architecture and use cases.
Looking forward to your details.
Hi, thanks for the quick reply. In our case, we have a secondary custom-written cache implementation for a particular type of ajax call that runs before Breeze’s full-page cache. So we need to know when Breeze updates the advanced-cache.php file, in order to add our own custom code into the file as well. Since this hook would only be used by advanced WordPress developers like myself, it wouldn’t affect regular Breeze users in any way, while providing users like us a way to run custom actions.