Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
consistent spelling#4671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
consistent spelling#4671
Changes fromall commits
5b8e84d
83238aa
85fb0b1
7eb1847
b2d802e
1bd33ca
f8db4b0
fd52cd3
9c02eda
95c842c
b774651
5b6895a
bd5ca26
07bc4db
6b7d536
f182121
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -55,7 +55,7 @@ On top of HttpFoundation is the :namespace:`Symfony\\Component\\HttpKernel` | ||
component. HttpKernel handles the dynamic part of HTTP; it is a thin wrapper | ||
on top of the Request and Response classes to standardize the way requests are | ||
handled. It also provides extension points and tools that makes it the ideal | ||
starting point to create aweb framework without too much overhead. | ||
It also optionally adds configurability and extensibility, thanks to the | ||
DependencyInjection component and a powerful plugin system (bundles). | ||
@@ -177,12 +177,12 @@ Event): | ||
#. Listeners of the ``kernel.terminate`` event can perform tasks after the | ||
Response has been served. | ||
If anexception is thrown during processing, the ``kernel.exception`` is | ||
notified and listeners are given a chance to convert theexception into a | ||
Response. If that works, the ``kernel.response`` event is notified; if not, the | ||
Exception is re-thrown. | ||
If you don't wantexceptions to be caught (for embedded requests for | ||
instance), disable the ``kernel.exception`` event by passing ``false`` as the | ||
third argument to the ``handle()`` method. | ||
@@ -238,8 +238,8 @@ add the following code at the beginning of your listener method:: | ||
.. tip:: | ||
If you are not yet familiar with the Symfony EventDispatcher component, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. I would like "Event Dispatcher component". There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Do you mean without the Symfony prefix? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. I mean with a space in the word. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Well, that's not really consistent with how we use component names otherwise (e.g. HttpFoundation, DependencyInjection, etc.). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. for example here we use so i am 👍 | ||
read:doc:`its documentation </components/event_dispatcher/introduction>` | ||
section first. | ||
.. index:: | ||
@@ -351,7 +351,7 @@ The FrameworkBundle registers several listeners: | ||
Collects data for the current request. | ||
:class:`Symfony\\Bundle\\WebProfilerBundle\\EventListener\\WebDebugToolbarListener` | ||
Injects theweb debug toolbar. | ||
:class:`Symfony\\Component\\HttpKernel\\EventListener\\ResponseListener` | ||
Fixes the Response ``Content-Type`` based on the request format. | ||
@@ -396,7 +396,7 @@ forwards the ``Request`` to a given Controller (the value of the | ||
``class::method`` notation). | ||
A listener on this event can create and set a ``Response`` object, create | ||
and set a new ``Exception`` object or do nothing:: | ||
use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent; | ||
use Symfony\Component\HttpFoundation\Response; | ||
@@ -433,8 +433,10 @@ and set a new ``Exception`` object, or do nothing:: | ||
.. index:: | ||
single: EventDispatcher | ||
.. _the-eventdispatcher: | ||
The EventDispatcher Component | ||
----------------------------- | ||
The EventDispatcher is a standalone component that is responsible for much | ||
of the underlying logic and flow behind a Symfony request. For more information, | ||
@@ -455,7 +457,7 @@ enhance performance; use it in the production environment to explore problems | ||
after the fact. | ||
You rarely have to deal with the profiler directly as Symfony provides | ||
visualizer tools like theweb debug toolbar and theweb profiler. If you use | ||
the Symfony Standard Edition, the profiler, the web debug toolbar, and the | ||
web profiler are all already configured with sensible settings. | ||
@@ -481,7 +483,7 @@ bottom of all pages. It displays a good summary of the profiling data that | ||
gives you instant access to a lot of useful information when something does | ||
not work as expected. | ||
If the summary provided by theweb debug toolbar is not enough, click on the | ||
token link (a string made of 13 random characters) to access the Web Profiler. | ||
.. note:: | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -207,7 +207,7 @@ The XML version of the config would then look like this: | ||
.. note:: | ||
In the Symfony full-stackFramework there is a base Extension class which | ||
implements these methods as well as a shortcut method for processing the | ||
configuration. See :doc:`/cookbook/bundles/extension` for more details. | ||
@@ -347,9 +347,9 @@ will then be called when the container is compiled:: | ||
.. note:: | ||
Compiler passes are registered differently if you are using the full-stack | ||
framework, see :doc:`/cookbook/service_container/compiler_passes` for | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. uppercase the F? or should it be: | ||
more details. | ||
Controlling the Pass Ordering | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
@@ -510,5 +510,5 @@ to see if the files have changed, if they have the cache will be considered stal | ||
.. note:: | ||
In the full-stack framework the compilation and caching of the container | ||
is taken care of for you. |
Uh oh!
There was an error while loading.Please reload this page.