-
-
Notifications
You must be signed in to change notification settings - Fork 704
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
InverseJoinColumn use statement omitted when migrating Doctrine entity from annotations to attributes #7528
Labels
Comments
greg0ire
added a commit
to greg0ire/doctrine-orm
that referenced
this issue
Oct 8, 2022
greg0ire
added a commit
to greg0ire/doctrine-orm
that referenced
this issue
Oct 8, 2022
greg0ire
added a commit
to greg0ire/doctrine-orm
that referenced
this issue
Oct 8, 2022
greg0ire
added a commit
to greg0ire/doctrine-orm
that referenced
this issue
Oct 9, 2022
Thank you for your report and demo link! Could you send a minimalistic failing test case in a pull-request, so we have it covered in Rector? |
Will try that in the coming days! |
Thanks. This property will be enough: /**
* @JoinTable(name="lemma_type",
* inverseJoinColumns={@JoinColumn(name="lemma_id", referencedColumnName="lemma_id")}
* )
*/
private Collection $lemmas; |
greg0ire
added a commit
to greg0ire/rector-src
that referenced
this issue
Oct 15, 2022
greg0ire
added a commit
to greg0ire/rector-src
that referenced
this issue
Oct 15, 2022
Done in rectorphp/rector-src#2987 🙂 |
TomasVotruba
pushed a commit
to rectorphp/rector-src
that referenced
this issue
Oct 15, 2022
TomasVotruba
pushed a commit
to rectorphp/rector-src
that referenced
this issue
Oct 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Minimal PHP Code Causing Issue
See https://getrector.org/demo/fb5d815a-c5fb-457f-939c-16403065fd67
Responsible rules
AnnotationToAttributeRector
NestedAnnotationToAttributeRector
Expected Behavior
Rector should do what it did AND add a use statement for
InverseJoinColumn
The text was updated successfully, but these errors were encountered: