8000 remove blank line after filepath in php code examples by OskarStark · Pull Request #11288 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

remove blank line after filepath in php code examples #11288

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 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 4, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 0 additions & 1 deletion bundles/configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -223,7 +223,6 @@ force validation (e.g. if an additional option was passed, an exception will be
thrown)::

// src/Acme/SocialBundle/DependencyInjection/AcmeSocialExtension.php

public function load(array $configs, ContainerBuilder $container)
{
$configuration = new Configuration();
Expand Down
1 change: 0 additions & 1 deletion components/console/changing_default_command.rst
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,6 @@ name to the ``setDefaultCommand()`` method::
Executing the application and changing the default command::

// application.php

use Acme\Console\Command\HelloWorldCommand;
use Symfony\Component\Console\Application;

Expand Down
1 change: 0 additions & 1 deletion components/yaml.rst
Original file line number Diff line number Diff line change
Expand Up @@ -415,7 +415,6 @@ First, install the Console component:
Create a console application with ``lint:yaml`` as its only command::

// lint.php

use Symfony\Component\Console\Application;
use Symfony\Component\Yaml\Command\LintCommand;

Expand Down
2 changes: 0 additions & 2 deletions configuration/micro_kernel_trait.rst
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,6 @@ putting *everything* in ``index.php``, create a new ``app/AppKernel.php`` to
hold the kernel. Now it looks like this::

// app/AppKernel.php

use Symfony\Bundle\FrameworkBundle\Kernel\MicroKernelTrait;
use Symfony\Component\Config\Loader\LoaderInterface;
use Symfony\Component\DependencyInjection\ContainerBuilder;
Expand Down Expand Up @@ -298,7 +297,6 @@ Finally, you need a front controller to boot and run the application. Create a
``web/index.php``::

// web/index.php

use Symfony\Component\HttpFoundation\Request;

require __DIR__.'/../app/AppKernel.php';
Expand Down
1 change: 0 additions & 1 deletion doctrine/pdo_session_storage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,6 @@ a second array arg 8000 ument to ``PdoSessionHandler``:
.. code-block:: php

// app/config/config.php

use Symfony\Component\HttpFoundation\Session\Storage\Handler\PdoSessionHandler;
// ...

Expand Down
3 changes: 0 additions & 3 deletions doctrine/resolve_target_entity.rst
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,6 @@ brevity) to explain how to set up and use the ``ResolveTargetEntityListener``.
A Customer entity::

// src/AppBundle/Entity/Customer.php

namespace AppBundle\Entity;

use Doctrine\ORM\Mapping as ORM;
Expand All @@ -60,7 +59,6 @@ A Customer entity::
An Invoice entity::

// src/Acme/InvoiceBundle/Entity/Invoice.php

namespace Acme\InvoiceBundle\Entity;

use Doctrine\ORM\Mapping AS ORM;
Expand All @@ -84,7 +82,6 @@ An Invoice entity::
An InvoiceSubjectInterface::

// src/Acme/InvoiceBundle/Model/InvoiceSubjectInterface.php

namespace Acme\InvoiceBundle\Model;

/**
Expand Down
1 change: 0 additions & 1 deletion form/dynamic_form_modification.rst
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,6 @@ Now that you have all the basics in place you can use the features of the
security helper to fill in the listener logic::

// src/AppBundle/Form/Type/FriendMessageFormType.php

use AppBundle\Entity\User;
use Doctrine\ORM\EntityRepository;
use Symfony\Bridge\Doctrine\Form\Type\EntityType;
Expand Down
1 change: 0 additions & 1 deletion form/form_collections.rst
Original file line number Diff line number Diff line change
Expand Up @@ -649,7 +649,6 @@ the relationship between the removed ``Tag`` and ``Task`` object.
is handling the "update" of your Task::

// src/AppBundle/Controller/TaskController.php

use AppBundle\Entity\Task;
use Doctrine\Common\Collections\ArrayCollection;

Expand Down
1 change: 0 additions & 1 deletion form/form_dependencies.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,6 @@ Suppose you need to access the :ref:`EntityManager <doctrine-entity-manager>` ob
so that you can make a query. First, add this as an argument to your form class::

// src/AppBundle/Form/TaskType.php

use Doctrine\ORM\EntityManagerInterface;
// ...

Expand Down
1 change: 0 additions & 1 deletion http_cache/cache_invalidation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,6 @@ Here is how you can configure the Symfony reverse proxy to support the
``PURGE`` HTTP method::

// app/AppCache.php

use Symfony\Bundle\FrameworkBundle\HttpCache\HttpCache;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\Response;
Expand Down
1 change: 0 additions & 1 deletion security/entity_provider.rst
Original file line number Diff line number Diff line change
Expand Up @@ -345,7 +345,6 @@ This extends :class:`Symfony\\Component\\Security\\Core\\User\\UserInterface`,
so you only need the new interface::

// src/AppBundle/Entity/User.php

use Symfony\Component\Security\Core\User\AdvancedUserInterface;
// ...

Expand Down
3 changes: 0 additions & 3 deletions service_container/factories.rst
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,6 @@ configure the service container to use the
.. code-block:: php

// app/config/services.php

use AppBundle\Email\NewsletterManager;
use AppBundle\Email\NewsletterManagerStaticFactory;
// ...
Expand Down Expand Up @@ -136,7 +135,6 @@ Configuration of the service container then looks like this:
.. code-block:: php

// app/config/services.php

use AppBundle\Email\NewsletterManager;
use AppBundle\Email\NewsletterManagerFactory;
use Symfony\Component\DependencyInjection\Reference;
Expand Down Expand Up @@ -216,7 +214,6 @@ example takes the ``templating`` service as an argument:
.. code-block:: php

// app/config/services.php

use AppBundle\Email\NewsletterManager;
use AppBundle\Email\NewsletterManagerFactory;
use Symfony\Component\DependencyInjection\Reference;
Expand Down
1 change: 0 additions & 1 deletion templating/PHP.rst
Original file line number Diff line number Diff line change
Expand Up @@ -279,7 +279,6 @@ Here, the ``AppBundle:Hello:fancy`` string refers to the ``fancy`` action of the
``Hello`` controller::

// src/AppBundle/Controller/HelloController.php

class HelloController extends Controller
{
public function fancyAction($name, $color)
Expand Down
1 change: 0 additions & 1 deletion workflow/state-machines.rst
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,6 @@ Below is the configuration for the pull request state machine.
.. code-block:: php

// app/config/config.php

$container->loadFromExtension('framework', [
// ...
'workflows' => [
Expand Down
1 change: 0 additions & 1 deletion workflow/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,6 @@ like this:
.. code-block:: php

// app/config/config.php

$container->loadFromExtension('framework', [
// ...
'workflows' => [
Expand Down
0