This is kind of uncommon in my opinion, isn't it? Wouldn't it be better to inject the request object to the custom ValidationListener, on a per-needed base? This way we would not pass the UploadedFile instance twice (once in the request object and once as a direct argument).

namespace Acme\EventListener;

use Symfony\Component\HttpFoundation\Request;
use Oneup\UploaderBundle\Event\ValidationEvent;

class CustomListener
{
    protected $request;

    public function __construct(Request $request)
    {
        $this->request = $request;
    }

    public function onValidate(ValidationEvent $event)
    {
        // custom logic
    }
}

And add the request object as an argument to your custom listener.

<service id="validation.custom" class="Acme\EventListener\CustomListener">
    <argument type="service" id="request" />
    <tag name="kernel.event_listener" event="oneup_uploader.validation" method="onValidate" />
</service>

Side note: This is untested. Maybe you have to set the scope of this service to request.
What do you think?

Pass the request to validation event #23

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions