10000 [DoctrineBridge] Dependency on a non existent service RegistryInterface · Issue #34377 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content

[DoctrineBridge] Dependency on a non existent service RegistryInterface #34377

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.

Sign up for GitHub

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

Jump to bottom
Closed
Matts opened this issue Nov 14, 2019 · 4 comments
Closed

[DoctrineBridge] Dependency on a non existent service RegistryInterface #34377

Matts opened this issue Nov 14, 2019 · 4 comments

Comments

@Matts
Copy link
Matts commented Nov 14, 2019 •
edited
Loading

Symfony version(s) affected: 4.4.0-BETA2

Description

When upgrading to 4.4, I got the following error
image

This most likely happened during the deprecation of the RegistryInterface (#32394) where possibly the class alias has been removed.

How to reproduce

App\Repository\Repository:
        arguments:
            - '@Symfony\Bridge\Doctrine\RegistryInterface'
        tags: ['doctrine.repository_service']

Possible Solution

Reregister the class alias

Additional context
@nicolas-grekas
Copy link
Member

This happens when you use Doctrine Bundle 2 - it's not related to the bridge.
See https://github.com/doctrine/DoctrineBundle/blob/master/UPGRADE-2.0.md

@Matts
Copy link
Author
Matts commented Nov 14, 2019

@nicolas-grekas Ah, so it is not a BC break due to this being a major version of Doctrine, gocha.

@Matt-PMCT
Copy link

This happens when you use Doctrine Bundle 2 - it's not related to the bridge.
See https://github.com/doctrine/DoctrineBundle/blob/master/UPGRADE-2.0.md

@nicolas-grekas For those of us that need a little more help (like the 500+ viewing this ). Can you give any advice on what the solution it is? Also I am unclear why the document you mentioned, as well as the Symfony Documentation, says to use Doctrine\Common\Persistence\ManagerRegistry when that is also deprecated and being removed?

@nicolas-grekas
Copy link
Member

That's because the deprecation happened after the linked document was written, like last week. Could you please send a PR to update it?

@GPHemsley GPHemsley mentioned this issue Sep 23, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nicolas-grekas @Matts @Matt-PMCT
0