100 lines
No EOL
5.8 KiB
JSON
100 lines
No EOL
5.8 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "fce16fe1-21a1-4db5-b1ee-f1ab3544ac90"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:13:01+00:00"
|
|
}
|
|
],
|
|
"revision_uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"revision_log": [],
|
|
"status": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"title": [
|
|
{
|
|
"value": "Which PHPStan level should you use?\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-11-28T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:13:01+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2023\/11\/28\/which-phpstan-level-should-you-use",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Which PHPStan level should you use?<\/p>\n\n<p>PHPStan has different levels.<\/p>\n\n<p>When you run it on your code, the errors you see will depend on what level you set.<\/p>\n\n<p><a href=\"http:\/\/localhost:8000\/daily\/2023\/11\/27\/finding-the-best-test-base\">In yesterday's email<\/a>, the first example code block didn't generate an error until level 5 was used.<\/p>\n\n<p>So, how do you know which level to use?<\/p>\n\n<h2 id=\"for-greenfield-projects\">For greenfield projects<\/h2>\n\n<p>For new (greenfield) code, install and configure PHPStan before you write any code and have and have it run automatically as part of a CI pipeline.<\/p>\n\n<p>If you work on a team, speak with the other members and decide how strict you want PHPStan to be.<\/p>\n\n<p>Read the rule levels and decide which are the most valuable for your team.<\/p>\n\n<p>If you haven't used PHPStan or static analysis before, maybe start with a lower level.<\/p>\n\n<p>For me, typehints and return type checking are a must, though I like to use as high a level as possible.<\/p>\n\n<p>The more information you can provide to PHPStan, the more it will understand your code, give better results and be more likely to find potential bugs or issues.<\/p>\n\n<h2 id=\"for-brownfield-projects\">For brownfield projects<\/h2>\n\n<p>For existing (brownfield) code, start at the lowest level, which will give you the least number of errors.<\/p>\n\n<p>Fix any errors, exclude any rules you want to ignore or generate a baseline containing any existing errors.<\/p>\n\n<p>If you like, increase the level and repeat the process.<\/p>\n\n<p>Keep increasing the level as long as you feel comfortable, and PHPStan gives you meaningful results.<\/p>\n\n<p>Again, if you haven't used PHPStan or static analysis before, maybe stick with a lower level.<\/p>\n\n<p>If you start with a lower level, you can increase it later.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Which PHPStan level should you use?<\/p>\n\n<p>PHPStan has different levels.<\/p>\n\n<p>When you run it on your code, the errors you see will depend on what level you set.<\/p>\n\n<p><a href=\"http:\/\/localhost:8000\/daily\/2023\/11\/27\/finding-the-best-test-base\">In yesterday's email<\/a>, the first example code block didn't generate an error until level 5 was used.<\/p>\n\n<p>So, how do you know which level to use?<\/p>\n\n<h2 id=\"for-greenfield-projects\">For greenfield projects<\/h2>\n\n<p>For new (greenfield) code, install and configure PHPStan before you write any code and have and have it run automatically as part of a CI pipeline.<\/p>\n\n<p>If you work on a team, speak with the other members and decide how strict you want PHPStan to be.<\/p>\n\n<p>Read the rule levels and decide which are the most valuable for your team.<\/p>\n\n<p>If you haven't used PHPStan or static analysis before, maybe start with a lower level.<\/p>\n\n<p>For me, typehints and return type checking are a must, though I like to use as high a level as possible.<\/p>\n\n<p>The more information you can provide to PHPStan, the more it will understand your code, give better results and be more likely to find potential bugs or issues.<\/p>\n\n<h2 id=\"for-brownfield-projects\">For brownfield projects<\/h2>\n\n<p>For existing (brownfield) code, start at the lowest level, which will give you the least number of errors.<\/p>\n\n<p>Fix any errors, exclude any rules you want to ignore or generate a baseline containing any existing errors.<\/p>\n\n<p>If you like, increase the level and repeat the process.<\/p>\n\n<p>Keep increasing the level as long as you feel comfortable, and PHPStan gives you meaningful results.<\/p>\n\n<p>Again, if you haven't used PHPStan or static analysis before, maybe stick with a lower level.<\/p>\n\n<p>If you start with a lower level, you can increase it later.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:13:01+00:00",
|
|
"guid": null,
|
|
"hash": "6bb6a39ea157159455db1b67897acb3a",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |