Problem/Motivation
Seems like the hal module is fighting until its last breath...
There are still a few references to it around in 10.0.x-dev even after its removal in #3049857: Remove HAL module from core and create a contrib project for it.
This issue is about the references in core/phpstan-baseline.neon which makes_any_ patch/MR against 10.0.x-dev altering core/phpstan-baseline.neon, which triggers a full PHPStan run, fail.
See for example https://www.drupal.org/pift-ci-job/2327905
Since this is slightly above just annoying, but blocks issues from getting in, put this on priority Major.
Steps to reproduce
Make change in core/phpstan-baseline.neon
See TestBot return red.
Proposed resolution
Remove remaining references to the hal module from core/phpstan-baseline.neon
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3266535
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3266535-remove-remaining-references
changes, plain diff MR !1890
Comments
Comment #3
spokjeComment #4
spokjeOne of these days I'll remember to change the *bleeping* assigned field in one go...
Comment #5
longwaveIMO this is critical as it is blocking commit of anything else.
Full run of PHPStan passed with this patch, therefore RTBC.
Comment #6
spokjeThanks @longwave!
Technically "Anything else that changes
core/phpstan-baseline.neonand thus triggers a full PHPStan run", but I'll happily take aCriticalany day...Comment #8
catchCommitted/pushed to 10.0.x, thanks for the quick follow-up!