Skip to content

Commit f1ef183

Browse files
committed
Fixes and rewords
1 parent 47aab81 commit f1ef183

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

best_practices.rst

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
The Symfony Framework Best Practices
22
====================================
33

4-
The Symfony Framework is well-known for being *really* flexible and is used to
5-
build from micro-sites to enterprise applications. This guide describes the
6-
**best practices for developing web applications with Symfony** that fit the
7-
philosophy envisioned by the original Symfony creators. You should only read
8-
this guide if you already have experience developing Symfony applications.
4+
This article describes the **best practices for developing web applications with
5+
Symfony** that fit the philosophy envisioned by the original Symfony creators.
96

10-
If you don't agree with some of these recommendations, this guide might be a good
7+
If you don't agree with some of these recommendations, they might be a good
118
**starting point** that you can then **extend and fit to your specific needs**.
12-
You can even ignore this guide completely and continue using your own best
13-
practices and methodologies. Symfony is flexible enough to adapt to your needs.
9+
You can even ignore them completely and continue using your own best practices
10+
and methodologies. Symfony is flexible enough to adapt to your needs.
11+
12+
This article assumes that you already have experience developing Symfony
13+
applications. If you don't, read first the rest of the `Symfony documentation`_.
1414

1515
.. tip::
1616

@@ -457,13 +457,14 @@ Hardcode URLs in a Functional Test
457457

458458
In Symfony applications it's recommended to :ref:`generate URLs <routing-generating-urls>`
459459
using routes to automatically update all links when a URL changes. However, if a
460-
URL changes, your public website will break unless you set up a redirection to
461-
the new URL.
460+
public URL changes, users won't be able to browse it unless you set up a
461+
redirection to the new URL.
462462

463463
That's why it's recommended to use raw URLs in tests instead of generating them
464464
from routes. Whenever a route changes, tests will break and you'll know that
465465
you must set up a redirection.
466466

467+
.. _`Symfony documentation`: https://symfony.com/doc
467468
.. _`Symfony Demo`: https://github.com/symfony/demo
468469
.. _`download Symfony`: https://symfony.com/download
469470
.. _`Composer`: https://getcomposer.org/

testing.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1054,7 +1054,6 @@ Learn more
10541054
:glob:
10551055

10561056
testing/*
1057-
/best_practices/tests
10581057
/components/dom_crawler
10591058
/components/css_selector
10601059

0 commit comments

Comments
 (0)