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
I registered extension twice in my config.neon.
Each instance for separated database, with separated migrations dir.
And it was working with some 3.0@dev version.
Now I try to update to 3.1@dev version. But migrations (dirs / Nextras\Migrations\Entities\Group) from each separated extension are mixed together. In each configuration (generated by extension) are present all groups.
Reason is probably in MigrationsExtension::createConfigurationDefinition.
It creates Nextras\Migrations\Configurations\Configuration with autowired constructor paramaterGroup[] $groups.
The solution would be to provide constructor parameters of Configuration directly without autoloading.
Version v3.1.0-rc2 is working.
The text was updated successfully, but these errors were encountered:
Hi,
Branch/commit:
master - 5970edad7945214a3eb5e22f74caa1cd35303b4d
.I registered extension twice in my
config.neon
.Each instance for separated database, with separated migrations dir.
And it was working with some
3.0@dev
version.Now I try to update to
3.1@dev
version.But migrations (dirs /
Nextras\Migrations\Entities\Group
) from each separated extension are mixed together. In each configuration (generated by extension) are present all groups.Reason is probably in
MigrationsExtension::createConfigurationDefinition
.It creates
Nextras\Migrations\Configurations\Configuration
with autowired constructor paramaterGroup[] $groups
.The solution would be to provide constructor parameters of
Configuration
directly without autoloading.Version
v3.1.0-rc2
is working.The text was updated successfully, but these errors were encountered: