Bug Report

When working on palantirnet/drupal-rector#419 I was chasing why it sometimes crashes and I couldnt work around some versions for the DrupalSetList. This was the analysis of it:

On a Drupal project with palantirnet/drupal-rector installed, the drupal toggle crashes at config load, before any file is processed:

[ERROR] Class "RectorPrefix202610\DrupalRector\Set\DrupalSetList" not found

Since 2.8.2, drupal/core is in ComposerBasedTriggerPackages, so a bare withComposerBased() turns on drupal: true automatically and hits the same crash.

Minimal PHP Code Causing Issue

<?php

use Rector\Config\RectorConfig;

return RectorConfig::configure()
    ->withPaths([__DIR__ . '/web/modules/custom'])
    ->withComposerBased(); // or ->withComposerBased(drupal: true)

Steps: Drupal 11 site, composer require --dev rector/rector:2.8.3 palantirnet/drupal-rector:dev-composer-based-set (the branch of palantirnet/drupal-rector#419 that adds DrupalSetList::COMPOSER_BASED), then run vendor/bin/rector process --dry-run.

Cause

src/Configuration/RectorConfigBuilder.php:

use DrupalRector\Set\DrupalSetList;                      // line 7
// ...
if ($drupal && class_exists('DrupalRector\Set\DrupalSetList') && constant('DrupalRector\Set\DrupalSetList::COMPOSER_BASED')) {
    $this->sets[] = DrupalSetList::COMPOSER_BASED;       // line 692
}

The string checks are left alone, but php-scoper prefixes the use import. scoper.php excludes #^Rector# (which is why RectorLaravel\… works) but not DrupalRector. Running from a rector-src checkout isn't scoped, so tests don't catch it.

Expected Behaviour

DrupalSetList::COMPOSER_BASED loads. Either fix works:

• add '#^DrupalRector#' to exclude-namespaces in scoper.php, or
• use $this->sets[] = constant('DrupalRector\Set\DrupalSetList::COMPOSER_BASED'); and drop the use import.