Skip to content

Commit 038f375

Browse files
committed
Rename includes directory to _includes
1 parent 75e0101 commit 038f375

File tree

6 files changed

+4
-5
lines changed

6 files changed

+4
-5
lines changed
File renamed without changes.

http_fundamentals.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -321,7 +321,7 @@ handles every request coming into your application. For example:
321321
| ``/index.php/blog`` | executes ``index.php`` |
322322
+------------------------+------------------------+
323323

324-
.. include:: /includes/_rewrite_rule_tip.rst.inc
324+
.. include:: /_includes/_rewrite_rule_tip.rst.inc
325325

326326
Now, every request is handled exactly the same way. Instead of individual URLs
327327
executing different PHP files, the front controller is *always* executed,

introduction/from_flat_php_to_symfony2.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ application change slightly, but start to become more flexible:
336336
/index.php => Blog post list page (index.php executed)
337337
/index.php/show => Blog post show page (index.php executed)
338338
339-
.. include:: /includes/_rewrite_rule_tip.rst.inc
339+
.. include:: /_includes/_rewrite_rule_tip.rst.inc
340340

341341
When using a front controller, a single PHP file (``index.php`` in this case)
342342
renders *every* request. For the blog post show page, ``/index.php/show`` will

service_container.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ for you. In order for this to work, you must *teach* the container how to
105105
create the ``Mailer`` service. This is done via configuration, which can
106106
be specified in YAML, XML or PHP:
107107

108-
.. include:: includes/service_container/_my_mailer.rst.inc
108+
.. include:: /_includes/service_container/_my_mailer.rst.inc
109109

110110
.. note::
111111

service_container/expression_language.rst

+1-2
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,7 @@ which has a ``getMailerMethod()`` method on it, which will return a string
1515
like ``sendmail`` based on some configuration. Remember that the first argument
1616
to the ``my_mailer`` service is the simple string ``sendmail``:
1717

18-
..
19-
.. include:: includes/_service_container_my_mailer.rst.inc
18+
.. include:: /_includes/service_container/_service_container_my_mailer.rst.inc
2019

2120
But instead of hardcoding this, how could we get this value from the ``getMailerMethod()``
2221
of the new ``mailer_configuration`` service? One way is to use an expression:

0 commit comments

Comments
 (0)