You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 1.17.11, with the introduction of searching in related entities (see #1910 and #1991), there is an DQL error (Class .... has no association named ....) when there are embedded entities in the relation. The easyadmin tries to join the embedded entity.
The text was updated successfully, but these errors were encountered:
There is a public property Doctrine\ORM\Mapping\ClassMetadataInfo::$embeddedClasses with the names of all embedded classes based on properties. Otherwise you could check by Doctrine\ORM\Mapping\ClassMetadataInfo::$associationMappings to make sure it's an association field.
I'm closing this issue because we're starting a new phase in the history of this bundle (see #2059). We've moved it into a new GitHub organization and we need to start from scratch: no past issues, no pending pull requests, etc.
I understand if you are angry or disappointed by this, but we really need to "reset" everything in order to reignite the development of this bundle.
This PR was squashed before being merged into the 1.x branch (closes#2209).
Discussion
----------
Allow embeddables 1 x
As discussed in #2065 , search with embeddables made the QueryBuilder fail, as it was treating them like Doctrine associations.
The changes in this PR corrects this behaviour, by using a more precise method of testing if a field is a Doctrine association
Commits
-------
6433cea Allow embeddables 1 x
Since version 1.17.11, with the introduction of searching in related entities (see #1910 and #1991), there is an DQL error (
Class .... has no association named ....
) when there are embedded entities in the relation. The easyadmin tries to join the embedded entity.The text was updated successfully, but these errors were encountered: