Skip to content

[Runtime] Minor fixes #15297

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 30, 2021
Merged

[Runtime] Minor fixes #15297

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions components/runtime.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ the component. This file runs the following logic:

#. It instantiates a :class:`Symfony\\Component\\Runtime\\RuntimeInterface`;
#. The callable (returned by ``public/index.php``) is passed to the Runtime, whose job
is to resolve the arguments (in this example: ``array $content``);
is to resolve the arguments (in this example: ``array $context``);
#. Then, this callable is called to get the application (``App\Kernel``);
#. At last, the Runtime is used to run the application (i.e. calling
``$kernel->handle(Request::createFromGlobals())->send()``).
Expand Down Expand Up @@ -172,12 +172,12 @@ a number of different applications are supported::
The ``SymfonyRuntime`` can handle these applications:

:class:`Symfony\\Component\\HttpKernel\\HttpKernelInterface`
The application will be run with :class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\HttpKernelRunner``
The application will be run with :class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\HttpKernelRunner`
like a "standard" Symfony application.

:class:`Symfony\\Component\\HttpFoundation\\Response`
The Response will be printed by
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ResponseRunner``::
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ResponseRunner`::

<?php
// public/index.php
Expand All @@ -191,7 +191,7 @@ The ``SymfonyRuntime`` can handle these applications:

:class:`Symfony\\Component\\Console\\Command\\Command`
To write single command applications. This will use the
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner``::
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner`::

<?php

Expand All @@ -211,7 +211,7 @@ The ``SymfonyRuntime`` can handle these applications:

:class:`Symfony\\Component\\Console\\Application`
Useful with console applications with more than one command. This will use the
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner``::
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner`::

<?php

Expand Down Expand Up @@ -361,7 +361,7 @@ class will have more control and can fix bugs and add features.

.. note::

Before Symfony 5.3, the Symfony boostrap logic was part of a Flex recipe.
Before Symfony 5.3, the Symfony bootstrap logic was part of a Flex recipe.
Since recipes are rarely updated by users, bug patches would rarely be
installed.

Expand All @@ -377,7 +377,7 @@ application outside of the global state in 6 steps:
represents the application.
#. This *application object* is passed to ``RuntimeInterface::getRunner()``, which
returns a :class:`Symfony\\Component\\Runtime\\RunnerInterface`: an instance
that knows how to "run" the appliction object.
that knows how to "run" the application object.
#. The ``RunnerInterface::run(object $application)`` is called and it returns the
exit status code as `int`.
#. The PHP engine is exited with this status code.
Expand Down