opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p>A couple of weeks ago, I wrote that <a href=\"/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n ",
"value": "\n <p>A couple of weeks ago, I wrote that <a href=\"\/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>A couple of weeks ago, I wrote that <a href=\"/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n ",
"processed": "\n <p>A couple of weeks ago, I wrote that <a href=\"http:\/\/default\/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "a4594c6103d2d62b9550cde5004820f8",
"target_type": "feeds_feed",