Hypervel\PHPStan\Collectors

Collects the calls to methods marked as boot-time or test-only, with the receiver evidence a worker-shared restriction needs. The rule judges them by the operation the call runs in.

Collects a try whose block runs an operation that can deliver cancellation, where the catch receiving the cancellation doesn't propagate it. The rule reports those that run in a request, job or operation.

Collects the unusable schema dumps of the connections whose models have undeclared properties read, so they are reported at the dumps themselves once the analysis has finished.

Collects the constant container resolutions that make a class worker-shared, the route closures that handle requests, the helpers a method calls on its own instance, and the config writes through the global repository.

Collects the classes that are worker-lifetime roots by declaration, the request or operation state their promoted constructor parameters keep, and the observers models register when they boot.

Collects the assignments and unset() calls that set or unset an offset of the global configuration repository, such as config()['app.locale'] = 'fr', which change it like Repository::set(). Each is read with the scope at the write, wherever it sits, such as inside a return or an arrow function.

Collects writes to global variables, which the whole worker shares like static properties: a $GLOBALS[...] write wherever it sits, and a write through a name a function's top-level global statement binds. Detecting the second walks the function's own statements, since PHPStan's scope doesn't say which variables are global. A request, user or model value written through a plain variable is collected too, so the rule can tell what such a global write keeps.

Collects the reassigned parameters whose injected values the worker-state checks rely on: a constructor's request or operation state, a configuration repository, and, for restricted calls, any method parameter that may hold an object.

Collects the property writes the worker-state checks may report: writes that keep request or operation state, request-keyed cache entries, and writes in methods that may run while handling a request or job.