-
-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the wrong CSRF token storage being wired #1625
Fix the wrong CSRF token storage being wired #1625
Conversation
…our own memory token storage
8aa8854
to
95f4dbc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain what the change does?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain how the change works?
What do you mean by explain? You want me to add a comment in the |
I had to read up on the Symfony docs 😇 So the issue is exactly the reason people argument that you should not use autowiring in a bundle. Now I wonder:
|
I was asking myself the same, I didn't understand why you guys did that.
How would that help? Was that maybe a mistake and you meant the |
Me neither. Who added this anyway? |
Hm, not really sure. I added the |
We‘re using Symfony‘s
Not really. We can add an interface as we, but the current issue is because our service uses a „default“ Symfony class. We‘d need to override/extend that to make autowiring work. |
I‘ve added „up for discussion“ because we probably want to talk about it tomorrow on Mumble. |
As discussed in Mumble on April, 9th, we want to merge the PR to fix the issue. |
Sorry, accidentally deleted the branch. |
Thank you @Toflar. |
If not specified explicitly, Symfony will autowire to the default CSRF token storage which is the session one :)