-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DoctrineBridge] [DX] Update exception text in ManagerRegistry to avoid confusion. #31047
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
[DoctrineBridge] [DX] Update exception text in ManagerRegistry to avoid confusion. #31047
Conversation
Failure is not related |
54cc1b6
to
ad4e2b4
Compare
Status: Needs Review |
…Service to avoid confusion.
ad4e2b4
to
9ade232
Compare
Thank you @Simperfit. |
…gistry to avoid confusion. (Simperfit) This PR was submitted for the master branch but it was merged into the 4.2 branch instead (closes #31047). Discussion ---------- [DoctrineBridge] [DX] Update exception text in ManagerRegistry to avoid confusion. | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yesish <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | no <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | #29659 <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | <!-- Write a short README entry for your feature/bugfix here (replace this comment block.) This will help people understand your PR and can be used as a start of the Doc PR. Additionally: - Bug fixes must be submitted against the lowest branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the master branch. --> Since the last PR was closed and the ticket is still open, taking it since it was already done by Nicolas in the comments. Commits ------- 9ade232 [DoctrineBridge] [DX] Update exception text in ManagerRegistry::resetService to avoid confusion.
@nicolas-grekas: Sorry but that just made the error message even more misleading in my case:
but it is already lazy, says my The problem is that Couldn't the code check that |
Nice suggestion, PR welcome :) |
@nicolas-grekas: I'm not sure how to do. Should I replace |
Please open an issue or a PR so that we can keep track of the discussion. |
…xt in ManagerRegistry to avoid confusion (guilliamxavier) This PR was submitted for the 4.4 branch but it was merged into the 4.3 branch instead. Discussion ---------- [DoctrineBridge] [DX] Improve condition for exception text in ManagerRegistry to avoid confusion | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yesish | New feature? | no | Deprecations? | no | Tickets | Fix #31047 (comment) | License | MIT | Doc PR | - (Targetting 4.4 because 4.3 is already almost EOM) Commits ------- 0d47fdf [DoctrineBridge] [DX] Improve condition for exception text in ManagerRegistry to avoid confusion
Since the last PR was closed and the ticket is still open, taking it since it was already done by Nicolas in the comments.