You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm doing #69 in my app (will send a PR later) and ran into a problem.
My extension catches the Symfony user token and stores it properly in the processor's token storage. But, to be able to use it, I must merge the user with the Doctrine entity manager (user must be managed to be able to use in Blameable or similar), all this works.
Problem was: after I merged the user, DoctrineClearIdentityMapExtension came in and cleared the map so my onPreReceived() ended up being useless. I've worked this by disabling it and doing the same thing from my onPostReceived, but the problem still remains: extensions should be able to specify their priority.
Also, shouldn't DoctrineClearIdentityMapExtension clear the map from onPostReceived, not onPreReceived?
The text was updated successfully, but these errors were encountered:
I'm doing #69 in my app (will send a PR later) and ran into a problem.
My extension catches the Symfony user token and stores it properly in the processor's token storage. But, to be able to use it, I must merge the user with the Doctrine entity manager (user must be managed to be able to use in Blameable or similar), all this works.
Problem was: after I merged the user,
DoctrineClearIdentityMapExtension
came in and cleared the map so myonPreReceived()
ended up being useless. I've worked this by disabling it and doing the same thing from myonPostReceived
, but the problem still remains: extensions should be able to specify their priority.Also, shouldn't
DoctrineClearIdentityMapExtension
clear the map fromonPostReceived
, notonPreReceived
?The text was updated successfully, but these errors were encountered: