Move daily emails into the blog page
This commit is contained in:
parent
be69398931
commit
1b8441608f
828 changed files with 9 additions and 196 deletions
33
source/_posts/2024-08-26.md
Normal file
33
source/_posts/2024-08-26.md
Normal file
|
@ -0,0 +1,33 @@
|
|||
---
|
||||
title: Named arguments add context
|
||||
date: 2024-08-26
|
||||
permalink: daily/2024/08/26/named-arguments-add-context
|
||||
tags:
|
||||
- software-development
|
||||
- drupal
|
||||
- php
|
||||
- automated-testing
|
||||
cta: ~
|
||||
snippet: |
|
||||
As well as types, PHP's named arguments also add context - particularly within tests.
|
||||
drupal_planet: true
|
||||
---
|
||||
|
||||
A couple of weeks ago, I wrote that [using types adds context to code][0], making it easier to read and understand.
|
||||
|
||||
Something else that also adds context is [named arguments][1], which were introduced to PHP in version 8.0.0.
|
||||
|
||||
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.
|
||||
|
||||
For example:
|
||||
|
||||
```php
|
||||
self::assertSame(expected: 'My Drupal website', actual: $node->label());
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
[0]: {{site.url}}/daily/2024/08/17/types-add-context
|
||||
[1]: https://www.php.net/manual/en/functions.arguments.php#functions.named-arguments
|
Loading…
Add table
Add a link
Reference in a new issue