Files
projectsend/app/Modules/Files/Thumbnails/Events/ImageRenderingChanged.php
ignacionelson 6e47d76ba6 ProjectSend 2.0.0
Client file sharing, rebuilt from the ground up: a private area per
client, resumable uploads, folders, groups and categories, sharing with
expiry dates and download limits, comments, file versions, an activity
log, a REST API, and sixteen languages.

This repository begins here. ProjectSend 2 was developed privately, and
that development history is not published — the previous generation
remains available, with its own history, at projectsend/legacy.

Free software under the GNU General Public License v2, or (at your
option) any later version.
2026-08-14 01:38:12 -03:00

33 lines
1.3 KiB
PHP

<?php
declare(strict_types=1);
namespace App\Modules\Files\Thumbnails\Events;
/**
* "Whatever RenderingImage listeners do now, they would do differently"
* — dispatched by whoever changes such a setting, so core can throw away
* the renditions it cached under the old rules.
*
* The return half of the RenderingImage seam. Rendered images are cached
* on disk and never regenerated once written (see
* FileThumbnailController), so a package that changes how they render
* has no way to make its own change visible: every already-viewed file
* keeps serving the stale bytes, potentially forever.
*
* It carries no payload, on purpose. That lets a package dispatch it by
* *string* class name without constructing a host class it cannot
* reference — the mirror image of how packages listen:
*
* Event::dispatch('App\Modules\Files\Thumbnails\Events\ImageRenderingChanged');
*
* With no host present that dispatch is an inert no-op, which is what
* keeps the package's own test suite runnable standalone.
*
* Flushing every rendition of every file is the right blunt instrument
* here: rendering settings are global, they change rarely and
* deliberately, and a rendition is a derived artifact that costs one
* lazy regeneration to rebuild.
*/
final class ImageRenderingChanged {}