Command Bus

This module is now part of the Developer Suite project and will be minimally maintained (bug fixes only).

Provides a ready-to-use command bus for developers. This module provides no interface but only an API for executing commands via a command bus. The command bus comes in handy if your application utilizes a service layer. For more information about service layers check out this great talk: https://www.youtube.com/watch?v=ajhqScWECMo.

Basic usage

1. Create your own Command class and extend the Drupalcommand_busCommandCommand class. The whole command class will be available in your CommandHandler class. Data needed for the command can be passed in the constructor and assigned to a public property for example.

<?php

namespace Drupalmy_moduleCommand;

use Drupalcommand_busCommandCommand;

/**
 * Class CreateData.
 */
class CreateData extends Command {
  
  public $data;

  public function __construct($data) {
    $this->data = $data;
  }

}

2. Create you own CommandHandler class and extend the Drupalcommand_busCommandCommand class. Please note: the handler class needs to live in the same namespace as your Command class and needs to be appended with Handler. For example: CreateData (command) and CreateDataHandler (command handler).

<?php

namespace Drupalmy_moduleCommand;

use Drupalcommand_busCommandCommandHandler;
use Drupalcommand_busValidatorViolations;
use DrupalCoreStringTranslationStringTranslationTrait;

/**
 * Class CreateDataHandler.
 */
class CreateDataHandler extends CommandHandler {

  use StringTranslationTrait;

  public function handle() {
    // Retrieve the command via the getCommand() method.
    $command = $this->getCommand();
    // Retrieve data from your command by calling its public properties.
    $data = $command->data;

    // Add your execution logic here.
  }

  public function rollback(Violations $violations) {
    // Add your rollback logic here. For example display violation messages.

    foreach ($violations->getViolations() as $violation) {
      drupal_set_message($this->t($violation->getMessage()), 'warning');
    }
  }

}

3. Instantiate your command, retrieve the command bus service and execute your command.

$data = [
    'foo' => 'bar',
  ];
$command = new CreateData($data);
Drupal::service('command_bus.default')->execute($command);

Command validation

The Command Bus provides methods to validate your command before and after executing. Validation is done in your Command class by setting validators via the addPreValidator() and addPostValidator() methods:

1. Create your validators. Create a validator class by extending the Drupalcommand_busValidatorValidator class. You can set a message on the public property $message for logging or displaying in your rollback() method.

<?php

namespace Drupal	estCommand;

use Drupalcommand_busValidatorValidator;
use Drupalcommand_busValidatorViolations;

class ValidOutcomeValidator extends Validator {

  public $message = 'Incorrect outcome.';

  public function validate($value, Violations $violations) {
    // If command output is not 'success', add a violation.
    if ($value !== 'success') {
      $violations->addViolation($this);
    }
  }

}

2. Attach your validators to your Command class. Multiple validators are allowed by calling the method again with a different validator.

<?php

namespace Drupalmy_moduleCommand;

use Drupalcommand_busCommandCommand;

/**
 * Class CreateData.
 */
class CreateData extends Command {
  
  public $data;

  public function __construct($data) {
    $this->data = $data;
    $this->addPreValidator(new SomeValidator());
    $this->addPostValidator(new ValidOutcomeValidator());
  }

}

There are 2 types of validators: pre and post validators. If a pre validator results in a violation the command is not run. If the post validator fails a rollback() method is invoked in your CommandHandler class passing the violations as the argument.

To do

- Support other command bus implementations such as Tactician.