Skip to content
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: error if translation contains ManyToMany including 'inversedBy' #35

Merged
merged 1 commit into from
Nov 24, 2022

Conversation

petrspevak
Copy link
Contributor

When I have used a CollectionType inside TranslationType and association included 'inversedBy', it caused an error about non-existent field. This solution worked for me and did not break anything else.

When I have used a CollectionType inside TranslationType and association included 'inversedBy', it caused an error about non-existent field.
@webda2l webda2l merged commit 50b8952 into a2lix:master Nov 24, 2022
@webda2l
Copy link
Member

webda2l commented Nov 24, 2022

Thanks!

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.

2 participants