Rector init should add Drupal-specific config in rector.php

Created on 3 July 2023, almost 2 years ago

Drupal version

Drupal version : 10.0.9

Drupal Rector version

Rector 0.15.25

Problem / Motivation

Running rector with no rector.php file in your codebase results in this prompt:

No "rector.php" config found. Should we generate it for you? [yes]:
> yes

[OK] The config is added now. Re-run command to make Rector do the work!

I was under the impression that this was giving me the proper rector.php file, but actually it's providing the base rector config, not the Drupal specific one. This results in basically no rector fixes being made.

Solution

Best: This module should hook into rector's init process to provide our config instead of theirs.

Less good: Warn folks that the auto-generated rector.php is good and redirect them to Create a config file in your project.

πŸ› Bug report
Status

Active

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States froboy Chicago, IL

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024