From 9736e2b480e6abb173972eb98e18c647ee002363 Mon Sep 17 00:00:00 2001 From: Drush Documentation Bot Date: Sat, 9 Mar 2024 21:53:59 +0000 Subject: [PATCH] Deployed 9cc6cd44a to 12.x with MkDocs 1.4.3 and mike 2.0.0 --- 12.x/bootstrap/index.html | 4 +- 12.x/commands/index.html | 6 +- 12.x/dependency-injection/index.html | 94 ++---- 12.x/generators/index.html | 4 +- 12.x/hooks/index.html | 4 +- 12.x/search/search_index.json | 2 +- 12.x/site-alias-manager/index.html | 9 +- 12.x/sitemap.xml | 470 +++++++++++++-------------- 12.x/sitemap.xml.gz | Bin 1865 -> 1865 bytes versions.json | 4 +- 10 files changed, 275 insertions(+), 322 deletions(-) diff --git a/12.x/bootstrap/index.html b/12.x/bootstrap/index.html index f78d9010d0..57472a87a6 100644 --- a/12.x/bootstrap/index.html +++ b/12.x/bootstrap/index.html @@ -5313,7 +5313,7 @@

The Drush Bootstrap Processnone

-

Only run Drush preflight, without considering Drupal at all. Any code that operates on the Drush installation, and not specifically any Drupal directory, should bootstrap to this phase.

+

Only run Drush preflight, without considering Drupal at all. Any code that operates on the Drush installation, and not specifically any Drupal directory, should bootstrap to this phase. This Attribute and value may also be used on a command class when it wants to load before Drupal bootstrap is started. Commands that ship inside Drupal modules always bootstrap to full, regardless of none value.

root

Set up and test for a valid Drupal root, either through the --root options, or evaluated based on the current working directory. Any code that interacts with an entire Drupal installation, and not a specific site on the Drupal installation should use this bootstrap phase.

site

@@ -5332,7 +5332,7 @@

max¶< Last update: - June 4, 2023 + March 9, 2024 diff --git a/12.x/commands/index.html b/12.x/commands/index.html index e50f997f25..2c6c6a9bd2 100644 --- a/12.x/commands/index.html +++ b/12.x/commands/index.html @@ -5269,7 +5269,7 @@

Creating Custom Commands

Tip

    -
  1. Drush 12 expects commandfiles to use a create() method to inject Drupal and Drush dependencies. Prior versions used a drush.services.yml file which is now deprecated and will be removed in Drush 13.
    2. +
  2. You may now use Autowire to inject Drupal and Drush dependencies. Prior approaches were using a [create() method](dependency-injection.md#create-method and using a drush.services.yml file. These are now deprecated.
  3. Drush 12 expects all commandfiles in the <module-name>/src/Drush/<Commands|Generators> directory. The Drush subdirectory is a new requirement.
@@ -5279,7 +5279,7 @@

Creating Custom CommandsDrush will prompt for the machine name of the module that should "own" the file. The module selected must already exist and be enabled. Use drush generate module to create a new module.
  • Drush will then report that it created a commandfile. Edit as needed.
  • Use the classes for the core Drush commands at /src/Commands as inspiration and documentation.
    • -
  • See the dependency injection docs for interfaces you can implement to gain access to Drush config, Drupal site aliases, etc. Also note the create() method for injecting Drupal or Drush dependencies.
    • +
  • You may inject dependencies into a command instance.
  • Write PHPUnit tests based on Drush Test Traits.

    • Attributes or Annotations

    @@ -5420,7 +5420,7 @@

    Global commands discovered Last update: - February 21, 2024 + March 9, 2024 diff --git a/12.x/dependency-injection/index.html b/12.x/dependency-injection/index.html index 2fa854857e..ee3372b111 100644 --- a/12.x/dependency-injection/index.html +++ b/12.x/dependency-injection/index.html @@ -705,8 +705,8 @@