From e80316b7879743b7a619a6fc3f834db4184c18d0 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Mon, 9 Jan 2017 17:22:47 +0100 Subject: [PATCH 1/2] Rename "console tasks" to "console commands" --- console/input.rst | 2 +- doctrine.rst | 2 +- doctrine/associations.rst | 2 +- doctrine/console.rst | 4 ++-- reference/dic_tags.rst | 2 +- security/acl.rst | 4 ++-- testing.rst | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/console/input.rst b/console/input.rst index 191569a9c60..ea6cd477d9e 100644 --- a/console/input.rst +++ b/console/input.rst @@ -134,7 +134,7 @@ Next, use this in the command to print the message multiple times:: $output->writeln($text); } -Now, when you run the task, you can optionally specify a ``--iterations`` +Now, when you run the command, you can optionally specify a ``--iterations`` flag: .. code-block:: terminal diff --git a/doctrine.rst b/doctrine.rst index b34e1342f2a..f34798c51d4 100644 --- a/doctrine.rst +++ b/doctrine.rst @@ -473,7 +473,7 @@ in your application. To do this, run: your entities) with how it *actually* looks, and executes the SQL statements needed to *update* the database schema to where it should be. In other words, if you add a new property with mapping metadata to ``Product`` - and run this task, it will execute the "ALTER TABLE" statement needed + and run this command, it will execute the "ALTER TABLE" statement needed to add that new column to the existing ``product`` table. An even better way to take advantage of this functionality is via diff --git a/doctrine/associations.rst b/doctrine/associations.rst index da0b7bc48a7..fde61496b55 100644 --- a/doctrine/associations.rst +++ b/doctrine/associations.rst @@ -18,7 +18,7 @@ the class for you. --entity="AppBundle:Category" \ --fields="name:string(255)" -This task generates the ``Category`` entity for you, with an ``id`` field, +This command generates the ``Category`` entity for you, with an ``id`` field, a ``name`` field and the associated getter and setter functions. Relationship Mapping Metadata diff --git a/doctrine/console.rst b/doctrine/console.rst index 7a126e44a6a..84d1cca146d 100644 --- a/doctrine/console.rst +++ b/doctrine/console.rst @@ -16,13 +16,13 @@ command: A list of available commands will print out. You can find out more information about any of these commands (or any Symfony command) by running the ``help`` command. For example, to get details about the ``doctrine:database:create`` -task, run: +command, run: .. code-block:: terminal $ php app/console help doctrine:database:create -Some notable or interesting tasks include: +Some notable or interesting commands include: * ``doctrine:ensure-production-settings`` - checks to see if the current environment is configured efficiently for production. This should always diff --git a/reference/dic_tags.rst b/reference/dic_tags.rst index 6f0b173fdce..8f36f0dbfa0 100644 --- a/reference/dic_tags.rst +++ b/reference/dic_tags.rst @@ -489,7 +489,7 @@ kernel.cache_warmer process Cache warming occurs whenever you run the ``cache:warmup`` or ``cache:clear`` -task (unless you pass ``--no-warmup`` to ``cache:clear``). It is also run +commands (unless you pass ``--no-warmup`` to ``cache:clear``). It is also run when handling the request, if it wasn't done by one of the commands yet. The purpose is to initialize any cache that will be needed by the application and prevent the first user from any significant "cache hit" where the cache diff --git a/security/acl.rst b/security/acl.rst index 2865cf0e1c0..a4d8b6c27ea 100644 --- a/security/acl.rst +++ b/security/acl.rst @@ -91,8 +91,8 @@ First, you need to configure the connection the ACL system is supposed to use: domain objects. You can use whatever mapper you like for your objects, be it Doctrine ORM, MongoDB ODM, Propel, raw SQL, etc. The choice is yours. -After the connection is configured, you have to import the database structure. -Fortunately, there is a task for this. Simply run the following command: +After the connection is configured, you have to import the database structure +running the following command: .. code-block:: terminal diff --git a/testing.rst b/testing.rst index f0311f60040..d541625fdbd 100644 --- a/testing.rst +++ b/testing.rst @@ -464,7 +464,7 @@ Injection Container:: $container = $client->getContainer(); For a list of services available in your application, use the ``debug:container`` -console task. +command. .. versionadded:: 2.6 Prior to Symfony 2.6, this command was called ``container:debug``. From 272aec338b7866eadec8c8203564ccce1c5bc24c Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Wed, 11 Jan 2017 09:42:03 +0100 Subject: [PATCH 2/2] Fixed a grammar error --- reference/dic_tags.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/dic_tags.rst b/reference/dic_tags.rst index 8f36f0dbfa0..329d8bef79c 100644 --- a/reference/dic_tags.rst +++ b/reference/dic_tags.rst @@ -489,7 +489,7 @@ kernel.cache_warmer process Cache warming occurs whenever you run the ``cache:warmup`` or ``cache:clear`` -commands (unless you pass ``--no-warmup`` to ``cache:clear``). It is also run +command (unless you pass ``--no-warmup`` to ``cache:clear``). It is also run when handling the request, if it wasn't done by one of the commands yet. The purpose is to initialize any cache that will be needed by the application and prevent the first user from any significant "cache hit" where the cache