We must consider dropping the CoreBundle in two ways.
In sonata-project bundles
Some CoreBundle classes extends -extensions classes. We can not change CoreBundle to -extensions in sonata-project bundles. We should change extends to class_alias. This will allow change API and drop CoreBundle in sonata-project bundles.
User must get information about deprecated in IDE. We must deprecated all CoreBundle classes. Some feature like FormHelper must be drop too becouse form type mapping is not support from 3.0 ?? We should also add "Bridge" to Form and Twig. This will allow resolve release problem. We will release CoreBundle, FormBundle and TwigBundle in one package:
Feature Request
We must consider dropping the CoreBundle in two ways.
In sonata-project bundles
Some CoreBundle classes extends -extensions classes. We can not change CoreBundle to -extensions in sonata-project bundles. We should change
extends
toclass_alias
. This will allow change API and drop CoreBundle in sonata-project bundles.Issue for that is here https://github.com/sonata-project/dev-kit/issues/697
In users projects
User must get information about deprecated in IDE. We must deprecated all CoreBundle classes. Some feature like FormHelper must be drop too becouse form type mapping is not support from 3.0 ?? We should also add "Bridge" to Form and Twig. This will allow resolve release problem. We will release CoreBundle, FormBundle and TwigBundle in one package:
and this package will be equal to next release:
I prepare v3.19 in 5 RPs:
CoreBundle v3.20: