base on Get error count for each PHPStan level # PHPStan Bodyscan [](https://packagist.org/packages/tomasvotruba/phpstan-bodyscan/stats) * Do you want to get quick glimpse of new project code quality? * Do you want to know, what PHPStan level is the best for your project? * Do you want to know, how much errors you're facing per level to see how hard it will be to reach them? Get error count for each PHPStan level! <br> ## How does it work? First, we look into the project root for `phpstan.neon` file. * If found, we reuse it. * If not, we look for defaults source code paths like `/src`, `/app`, `/tests`, etc. Then we run PHPStan for each level from 0 to 8. We count errors and display them in a table. <br> ## Install ```bash composer require tomasvotruba/phpstan-bodyscan --dev ``` ## Usage Run tool in your project. It will take some time, as it will run full PHPStan analysis for each level. ```bash vendor/bin/phpstan-bodyscan ``` ↓ To get errors count per level: ```bash +-------+-------------+-----------+ | Level | Error count | Increment | +-------+-------------+-----------+ | 0 | 0 | - | | 1 | 35 | + 35 | | 2 | 59 | + 24 | | 3 | 59 | - | | 4 | 120 | + 61 | | 5 | 120 | - | | 6 | 253 | + 133 | | 7 | 350 | + 97 | | 8 | 359 | + 9 | +-------+-------------+-----------; ``` <br> ## Do you want to run levels including all ignored messages? ```bash vendor/bin/phpstan-bodyscan --no-ignore ``` <br> ## Do you want to run levels without extensions? ```bash vendor/bin/phpstan-bodyscan --bare ``` <br> ## Do you need a JSON format? We got you covered: ```bash vendor/bin/phpstan-bodyscan --json ``` ↓ ```bash [ { "level": 0, "error_count": 0, "increment_count": 0 }, { "level": 1, "error_count": 5, "increment_count": 5 }, { "level": 2, "error_count": 25, "increment_count": 20 } ] ``` <br> ### Limit level count Are you interested only in a few levels? You can limit ranges by the options: ```bash vendor/bin/phpstan-bodyscan run --min-level 0 --max-level 3 ``` <br> ### Measure type coverage *Experimental!* Are you interested in learning param, return and property type declaration coverage of the project? Run `type-coverage` command ↓ ```bash vendor/bin/phpstan-bodyscan type-coverage --json ``` ↓ ```php [ { "category": "param type", "relative_covered": 100, "total_count": 54 }, { "category": "property type", "relative_covered": 100, "total_count": 1 }, { "category": "return type", "relative_covered": 100, "total_count": 33 }, { "category": "strict declares", "relative_covered": 100, "total_count": 18 } ] ``` Based on [type-coverage package](https://github.com/TomasVotruba/type-coverage). <br> ### Load env file Some projects need to load `.env` file to run PHPStan. You can do it like this: ```bash vendor/bin/phpstan-bodyscan run --env-file some-parameters.env ``` <br> ### Debugging Running PHPStan on a new project you don't know might crash. To save data from finished levels, we dump them to the `bodyscan-log.txt` file. If the run crashes for any reason, the PHPStan error output is also dumped to the same file. <br> Happy coding! ", Assign "at most 3 tags" to the expected json: {"id":"9911","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"