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
From #1037, the WellKnownSchemaFilterPass works overall, but the Messenger part was flawed. There is no Connection service that is added when the Doctrine transport is active. Instead, (check FrameworkExtension), for each transport, a factory is used to create the transport. It's quite dynamic, unfortunately (to support env vars), which makes it impossible to see at container build time which type of transport it will use.
I'm not sure of a good solution - I'm hoping @nicolas-grekas might have an idea!
The text was updated successfully, but these errors were encountered:
This issue is still waiting on feedback. Please provide the information requested above to allow us to continue working on this ticket.
This issue will be closed after 7 days. You can still provide us with the necessary information to continue working on this issue, and we will reopen the ticket for you. Thanks!
This issue is still waiting on feedback. Please provide the information requested above to allow us to continue working on this ticket.
This issue will be closed after 7 days. You can still provide us with the necessary information to continue working on this issue, and we will reopen the ticket for you. Thanks!
From #1037, the
WellKnownSchemaFilterPass
works overall, but the Messenger part was flawed. There is noConnection
service that is added when the Doctrine transport is active. Instead, (checkFrameworkExtension
), for each transport, a factory is used to create the transport. It's quite dynamic, unfortunately (to support env vars), which makes it impossible to see at container build time which type of transport it will use.I'm not sure of a good solution - I'm hoping @nicolas-grekas might have an idea!
The text was updated successfully, but these errors were encountered: