- Issue created by @fgm
- 🇳🇱Netherlands bbrala Netherlands
Wow interesting, wonder what broke this.
How to reproduce:
- install drupal 10
- composer require drupal/g2:dev-11.x#922c101dbbcc1785263854d8bb0747f10fb89f7d
- composer require palantirnet/drupal-rector
- cp vendor/palantirnet/drupal-rector/rector.php .
- vendor/bin/rector --dry-run
This should also print what rules were used, if not, up the verbosity of rector.
When we know what rule broke this, we can add a test for this pattern to that rule and fix it.
- 🇫🇷France fgm Paris, France
I wonder: should I be expecting any news on this, or just forget about rector since the module is already compatible with D11 anyway and the ugprade bot keeps pushing nonsense on 📌 Automated Drupal 11 compatibility fixes for g2 Needs review ?
- 🇳🇱Netherlands bbrala Netherlands
Asked for somw extra info, but i think i also checked upstream and posted a patch.
https://github.com/rectorphp/rector-symfony/pull/610
Appearantly this did not fix the issue?
Im back from vacation next week and will do some issue queue maintenace.