Baseline feature

[staabm]

Similar to psalm and phpstan it would be helpfull to integrate the tool in already existing code bases by providing a baseline feature.

A baseline allows you to define all rules and make sure all newly written code will obey these rules, without the need to fix the whole codebase for violations

See details in

https://medium.com/@ondrejmirtes/phpstans-baseline-feature-lets-you-hold-new-code-to-a-higher-standard-e77d815a5dff
https://psalm.dev/docs/running_psalm/dealing_with_code_issues/#using-a-baseline-file

[carlosas]

I'm doing this with a pre-commit hook that extracts the changed files in the commit and modifies the phpat.yaml include option so the tests only include this files (this config is taken in the StatementBuilder).
https://gist.github.com/carlosas/36206cd95354245836226a9b3bb2a947
Is it the same result or does a baseline file bring something more?

Anyway the way I do it is a bit clunky, it would be a nice extra feature to implement.
Are you up for it? 😛

[staabm]

I might work on such a feature when phpat gehts relevant for our projects.

atm. we need to setup other QA things first.

[smoench]

You might have a look at https://github.com/DaveLiddament/sarb :-)

[carlosas]

Released with https://github.com/carlosas/phpat/releases/tag/0.8.0 🙂