The issue is that the validateFields function potentially used on on Action, doesn't properly handle that an action doesn't need to call $this->action()->fields() and instead could call $this->fields() directly.
This PR breaks up the monolithic HasDependencies into multiple smaller traits, and specifically documents how to use the Dependency Container in an Action.
Maybe this is actually enabling using dependency on actions
This fixes a seemingly outlier issue potentially related to opcache, where the ActionRequest is called on an Action.
The stacktrace here looks something like this:
The issue is that the validateFields function potentially used on on Action, doesn't properly handle that an action doesn't need to call
$this->action()->fields()
and instead could call$this->fields()
directly.This PR breaks up the monolithic HasDependencies into multiple smaller traits, and specifically documents how to use the Dependency Container in an Action.
Maybe this is actually enabling using dependency on actions