CacheClearReport
class CacheClearReport
What clearing the cache actually did.
Kept separate from how it is presented: the console renders it as a table, the API hands it to the admin panel as JSON. Each step records what happened rather than a sentence about it, so the words can come from the translations on whichever side is doing the rendering — a formatted string built here would be English for ever.
Constants
| UNCHANGED |
|
| REBUILT |
|
| REWRITTEN |
|
| EMPTY |
|
| CHUNKS |
|
Methods
One compiled bundle.
The split chunks of one frontend, which have a revision each rather than one between them, so only a count of what moved is meaningful.
A step that could not be pre-built. The cache is already cleared by the time any of them run, so these are reported rather than fatal.
Details
at
line 71
__construct(callable|null $listener = null)
at
line 76
void
cleared(string $name, int|null $files = null)
at
line 98
void
rebuilt(string $frontend, string|null $locale, string|null $localeName, string $bundle, string $state, string|null $revision, string|null $previousRevision, int|null $bytes, float $seconds)
One compiled bundle.
`$state` says what happened to it — see the constants above — so a renderer can decide whether a revision, a size or neither is worth showing without parsing anything.
at
line 127
void
rebuiltChunks(string $frontend, int $changed, float $seconds)
The split chunks of one frontend, which have a revision each rather than one between them, so only a count of what moved is meaningful.
at
line 147
void
failed(string $step, string $message)
A step that could not be pre-built. The cache is already cleared by the time any of them run, so these are reported rather than fatal.