Skip to content

Fixing a bug where the wrong ManagerRegistry was sometimes used in repositories #591

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

Merged
merged 1 commit into from
Apr 21, 2020

Conversation

weaverryan
Copy link
Member

@weaverryan weaverryan commented Apr 21, 2020

This problem occurs if using DoctrineBundle 1.11 or lower, where the newer Persistence
alias is not available. This also centralizes the creation of the repository classes
to fix this in all places.

Problem introduced in #570

@weaverryan weaverryan force-pushed the fix-wrong-manager-registry branch from 5a7b899 to f3c1b25 Compare April 21, 2020 18:18
…positories

This problem occurs if using DoctrineBundle 1.11 or lower, where the newer Persistence
alias is not available. This also centralizes the creation of the repository classes
to fix this in all places.
@weaverryan weaverryan force-pushed the fix-wrong-manager-registry branch from f3c1b25 to 30846ca Compare April 21, 2020 18:46
@weaverryan weaverryan merged commit ae95a2b into master Apr 21, 2020
@weaverryan weaverryan deleted the fix-wrong-manager-registry branch April 21, 2020 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant