@@ -53,8 +53,8 @@ The above example can be updated to work with Symfony 3 as follows:
5353Looking for Deprecations and Fix Them
5454-------------------------------------
5555
56- Besides allowing to install Symfony 3 packages , your bundle must stop using
57- any feature deprecated in 2.8 version, because they are removed (and you'll get
56+ Besides allowing users to use your bundle with Symfony 3, your bundle must stop using
57+ any feature deprecated by the 2.8 version because they are removed in 3.0 ( you'll get
5858exceptions or PHP errors). The easiest way to detect deprecations is to install
5959the `symfony/phpunit-bridge package `_ and then run the test suite.
6060
@@ -185,32 +185,6 @@ adding a ``setDefined()`` method. The recommended check in this case would be::
185185 // code for the new OptionsResolver API
186186 }
187187
188- Form Name Refactoring
189- ~~~~~~~~~~~~~~~~~~~~~
190-
191- .. TODO
192-
193- - how to check which version to use
194- - how to update FormType classes
195- - how to update type service definitions
196- - how to update FormTypeExtension classes & service definition
197-
198-
199- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
200-
201- .. TODO
202-
203- - how to check which version to use
204- - how to both APIs
205-
206-
207- ~~~~~~~~~~~~~~~~~~~~~~~~~~~
208-
209- .. TODO
210-
211- - how to support both APIs ==> Is there a nice way except from (a) doing
212- it in the DI extension or (b) creating 2 service definition files?
213-
214188.. _`symfony/phpunit-bridge package` : https://github.com/symfony/phpunit-bridge
215189.. _`Official Symfony Guide to Upgrade from 2.x to 3.0` : https://github.com/symfony/symfony/blob/2.8/UPGRADE-3.0.md
216190.. _`SensioLabs DeprecationDetector` : https://github.com/sensiolabs-de/deprecation-detector
0 commit comments