| Q |
A |
| Bug report? |
no |
| Feature request? |
yes |
| Library version |
2.11.0 |
Would be great to be able to disable each of the broad-category checks that PHPInsights does, such as styling. We use Laravel pint, so we don't need to double-up on styling (this is also a central part of our git-commit pipeline - it automatically applies any fixes required before the code reaches the repository).
I have not yet found a way how to disable this completely. We do however, want to keep insights for the rest, as we've found it very useful, and intend on using it as part of our github actions deployment checks, but currently due to it highlighting style issues that are not in alignment with our Pint configuration, this becomes quite difficult.
Alternatively, have phpinsights read from the pint configuration file and configure it's own styling checks that way.
Would be great to be able to disable each of the broad-category checks that PHPInsights does, such as styling. We use Laravel pint, so we don't need to double-up on styling (this is also a central part of our git-commit pipeline - it automatically applies any fixes required before the code reaches the repository).
I have not yet found a way how to disable this completely. We do however, want to keep insights for the rest, as we've found it very useful, and intend on using it as part of our github actions deployment checks, but currently due to it highlighting style issues that are not in alignment with our Pint configuration, this becomes quite difficult.
Alternatively, have phpinsights read from the pint configuration file and configure it's own styling checks that way.