-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[DoctrineBridge] Deprecate passing doctrine subscribers to ContainerAwa… #18181
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
Labels
Milestone
Comments
I found no reference for |
Closing then. |
this is not passed explicitly in the doc, because the wiring is done by DoctrineBundle. But https://symfony.com/doc/current/doctrine/events.html#doctrine-lifecycle-subscribers still documents subscribers. So this should be reopened. |
javiereguiluz
added a commit
that referenced
this issue
Sep 19, 2023
…iereguiluz) This PR was squashed before being merged into the 6.3 branch. Discussion ---------- [Doctrine] Update the article about Doctrine events Fixes #18650 and #18181. Changes in this PR: * Reworded the introduction to only explain the 3 types of listeners which are not deprecated and better explain why/when to use them according to #18650 * Reordered the explanation of the listeners to match the same order as in the intro: `Lifecycle callbacks` -> `Entity listeners` -> `Lifecycle listeners` * Removed the contents about "Lifecycle Subscribers" because they are deprecated Commits ------- 4a4d9de [Doctrine] Update the article about Doctrine events
Closing as fixed in #18878. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We created this issue to not forget to document this new feature. We would really appreciate if you can help us with this task. If you are not sure how to do it, please ask us and we will help you.
To fix this issue, please create a PR against the 6.3 branch in the symfony-docs repository.
Thank you! 😃
The text was updated successfully, but these errors were encountered: