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
Configuration of entity mapping is ambiguous because it can be added globally via provider from extensions or per instance via configuration to EntityManager. But the global from extensions overrides the specific from configuration.
The text was updated successfully, but these errors were encountered:
Sorry my bad, I was already editing the issue, but will reply bellow instead.
Then it is just a minor issue. If I want another EntityManager with only specific Entities I will get those + global from provider. There is no way to disable them in config. So specific configuration does not make much sense. I guess there might be some edge cases where it makes sense, but I have to jet discover them.
Current behaviour is a bit confusing.
Configuration of entity mapping is ambiguous because it can be added globally via provider from extensions or per instance via configuration to EntityManager. But the global from extensions overrides the specific from configuration.
The text was updated successfully, but these errors were encountered: