-
Notifications
You must be signed in to change notification settings - Fork 59
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
Extension system #377
Comments
This block of code is literally the configuration of this utility: BackwardCompatibilityCheck/bin/roave-backward-compatibility-check.php Lines 82 to 311 in d4c84f0
The current way you customize it is by copying the whole BackwardCompatibilityCheck/bin/roave-backward-compatibility-check.php Lines 55 to 81 in d4c84f0
Even then, it is not uncommon that the Requiring BackwardCompatibilityCheck/bin/roave-backward-compatibility-check.php Lines 38 to 53 in d4c84f0
I thought about how to make this "easier to customize", but in practice, it is better to:
So don't feel dirty about it: it's still the best way forward, and if you needed to change one tiny check 10 levels deep in the structure, you still have to rewrite the whole instantiation chain anyway :) One simplification I thought of is unifying |
Hey,
we're currently adding custom checks into this tool using composer patches. I feel really dirty to add a custom check into the list of https://github.com/Roave/BackwardCompatibilityCheck/blob/6.1.x/bin/roave-backward-compatibility-check.php#L86
I guess a simple extension system could help here already to add custom checks.
What I think is:
getClassChecks
getMethodChecks
... which returns the instancesextra
part in the composer.jsonroave-backward-compatibility-check.php
or maybe move the core things to the same interface based thingy?The text was updated successfully, but these errors were encountered: