Skip to main content
Drupal API
User account menu
  • Log in

Breadcrumb

  1. Drupal Core 11.1.x
  2. ValidateCommand.php

function ValidateCommand::configure

configure

Overrides Command::configure

File

vendor/composer/composer/src/Composer/Command/ValidateCommand.php, line 40

Class

ValidateCommand
ValidateCommand

Namespace

Composer\Command

Code

protected function configure() : void {
    $this->setName('validate')
        ->setDescription('Validates a composer.json and composer.lock')
        ->setDefinition([
        new InputOption('no-check-all', null, InputOption::VALUE_NONE, 'Do not validate requires for overly strict/loose constraints'),
        new InputOption('check-lock', null, InputOption::VALUE_NONE, 'Check if lock file is up to date (even when config.lock is false)'),
        new InputOption('no-check-lock', null, InputOption::VALUE_NONE, 'Do not check if lock file is up to date'),
        new InputOption('no-check-publish', null, InputOption::VALUE_NONE, 'Do not check for publish errors'),
        new InputOption('no-check-version', null, InputOption::VALUE_NONE, 'Do not report a warning if the version field is present'),
        new InputOption('with-dependencies', 'A', InputOption::VALUE_NONE, 'Also validate the composer.json of all installed dependencies'),
        new InputOption('strict', null, InputOption::VALUE_NONE, 'Return a non-zero exit code for warnings as well as errors'),
        new InputArgument('file', InputArgument::OPTIONAL, 'path to composer.json file'),
    ])
        ->setHelp(<<<EOT
The validate command validates a given composer.json and composer.lock

Exit codes in case of errors are:
1 validation warning(s), only when --strict is given
2 validation error(s)
3 file unreadable or missing

Read more at https://getcomposer.org/doc/03-cli.md#validate
EOT
);
}

API Navigation

  • Drupal Core 11.1.x
  • Topics
  • Classes
  • Functions
  • Constants
  • Globals
  • Files
  • Namespaces
  • Deprecated
  • Services
RSS feed
Powered by Drupal