Maxime Steinhausser

That's particularly annoying to do this for the `BackedEnumValueResolver` since it would not even to be used, but to trigger a deprecation for the end user to switch to the...

Hi. Did you clear the cache in prod env in between your changes? ```sh symfony console c:c -e prod ```

I didn't encounter such an issue so far, though 🤷🏻‍♂️

I don't get how it is related to this package though ?

Thanks for notifying. Considering the few changes in this PR about doctrine, do you really think it'll require much more efforts to maintain both versions support in 2.x?

Hi. Is there any progress status about this feature request ?

I can't remember now, I should give it another try. But I guess it didn't if I tried to authenticate through the URI. :/

We use skipped migrations for migrations that should run only in some envs, or on a specific database when the application has multiple connections. So it seems obvious to me...

Currently I by-pass the listener, overriding the it by this one: ``` yaml services: #Overrides AuthenticationListener from PUGXMultiUserBundel pugx_multi_user.listener.authentication: class: Acme\UserBundle\Listeners\Security\AuthenticationListener arguments: ["@pugx_user.manager.user_discriminator", %fos_user.model.user.class%] tags: - { name: kernel.event_subscriber }...

Still relevant AFAIK