Current context is Pull 762 that adds the much needed migrations framework.
Since this adds things to mapbender lib, the requirement should also go into mapbender lib's composer.json.
This also depends on having the DoctrineMigrationsBundle registered, which is an AppKernel-level change. AppKernel resides in mapbender starter. So we cannot cleanly do one thing in one pull, we have to order them in a certain way and put up warning signs to people to update in the "correct" (TBD) order.
I'm proposing a bigger decoupling of Mapbender starter and Mapbender lib by adding a Mapbender\BaseKernel (inside Mapbender lib) from which the actual booting AppKernel (in Mapbender starter) can inherit.
People who do not update their starters would see no change at all.
Bundles required by Mapbender lib can then be maintained in Mapbender lib, completely.
Current context is Pull 762 that adds the much needed migrations framework.
Since this adds things to mapbender lib, the requirement should also go into mapbender lib's composer.json.
This also depends on having the DoctrineMigrationsBundle registered, which is an AppKernel-level change. AppKernel resides in mapbender starter. So we cannot cleanly do one thing in one pull, we have to order them in a certain way and put up warning signs to people to update in the "correct" (TBD) order.
I'm proposing a bigger decoupling of Mapbender starter and Mapbender lib by adding a Mapbender\BaseKernel (inside Mapbender lib) from which the actual booting AppKernel (in Mapbender starter) can inherit.
People who do not update their starters would see no change at all.
Bundles required by Mapbender lib can then be maintained in Mapbender lib, completely.