-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable PHPStan Extensions outside of bleeding edge #31
Conversation
Composer\Pcre\PHPStan\UnsafeStrictGroupsCallRule: | ||
phpstan.rules.rule: %featureToggles.narrowPregMatches% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw: I think this UnsafeStrictGroupsCallRule
conditional tag didn't work as expected because we always registered the class as a rule at line 21.
to make this conditional-tag work, we should have registered the rule as a service without a tag (and not below the rules:
section) -> I think the rule was enabled no matter bleeding edge
Yeah I'd say let's remove it.. |
I agree. people can stick with 2.2.0 or 3.2.0 in case a PHPStan-src fix is needed for some edge-case array-shape matching. |
regarding the failed build: I found sebastianbergmann/phpunit#5062 but could not yet find a way to repair the build (unrelated to the actual PR) |
Put it back to draft, because I want to look into preg_match_all() before we drop bleeding edge |
Thanks |
ondrej enabled the preg-match $matches inference feature with 1.12.x by default as it seems stable enough for general use.
the feature flag
%featureToggles.narrowPregMatches%
we rely on will be dropped with 1.12.so there are 2 possible ways to handle it:
@Seldaek wdyt about this options. do you feel confident to remove the feature flag for bleeding edge already within composer/pcre?