Skip to content

Commit c7deeef

Browse files
committed
minor symfony#9983 [Routing] do not install SensioFrameworkExtraBundle (Tobion, javiereguiluz)
This PR was merged into the 4.0 branch. Discussion ---------- [Routing] do not install SensioFrameworkExtraBundle The routing annotations of SensioFrameworkExtraBundle are deprecate since sensiolabs/SensioFrameworkExtraBundle#562 Also the example code in this documentation does not use SensioFrameworkExtraBundle at all but the core annotation as it should be. So installing the SensioFrameworkExtraBundle is pointless. <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- c98babf Reword 6119b67 [Routing] do not install SensioFrameworkExtraBundle
2 parents a2864b3 + c98babf commit c7deeef

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

routing.rst

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,19 @@ the change is simple.
2020
Creating Routes
2121
---------------
2222

23-
First, add support for annotations via the SensioFrameworkExtraBundle:
23+
A *route* is a map from a URL path to a controller. Suppose you want one route that
24+
matches ``/blog`` exactly and another more dynamic route that can match *any* URL
25+
like ``/blog/my-post`` or ``/blog/all-about-symfony``.
26+
27+
Routes can be configured in YAML, XML and PHP. All formats provide the same
28+
features and performance, so choose the one you prefer. If you choose PHP
29+
annotations, run this command once in your app to add support for them:
2430

2531
.. code-block:: terminal
2632
27-
$ composer require sensio/framework-extra-bundle
33+
$ composer require annotations
2834
29-
A *route* is a map from a URL path to a controller. Suppose you want one route that
30-
matches ``/blog`` exactly and another more dynamic route that can match *any* URL
31-
like ``/blog/my-post`` or ``/blog/all-about-symfony``:
35+
Now you can configure the routes:
3236

3337
.. configuration-block::
3438

0 commit comments

Comments
 (0)