for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace CultuurNet\UDB3\EventSourcing;
use Broadway\Domain\DateTime;
use Broadway\Domain\DomainMessage;
use Broadway\Domain\Metadata;
use ValueObjects\Identity\UUID;
/**
* Helper class for building domain messages, to be used in automated tests.
*/
class DomainMessageBuilder
{
* @var string $userId
private $userId;
* @var string $id
private $id;
* @var int
private $playhead;
* @var DateTime
private $recordedOn;
public function setId(string $id): self
$this->id = $id;
return $this;
}
public function setUserId(string $userId): self
$this->userId = $userId;
public function setRecordedOnFromDateTimeString(string $dateTime): self
$this->recordedOn = DateTime::fromString($dateTime);
public function setPlayhead(int $i): self
$this->i = $i;
i
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
class MyClass { } $x = new MyClass(); $x->foo = true;
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:
class MyClass { public $foo; } $x = new MyClass(); $x->foo = true;
* @return \Broadway\Domain\DomainMessage
public function create($payload)
$finalMetaData = new Metadata();
$finalMetaData = $finalMetaData->merge(
new Metadata(
[
'user_id' => $this->userId ?? UUID::generateAsString(),
]
)
);
return new DomainMessage(
$this->id ?? UUID::generateAsString(),
$this->playhead ?? 1,
$finalMetaData,
$payload,
$this->recordedOn ?? DateTime::now()
cultuurnet /
udb3-php
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: