not
b496ac9477
CI / build (pull_request) Successful in 1m11s
CI / lint (pull_request) Successful in 1m25s
CI / unit (pull_request) Successful in 1m27s
CI / frontend (pull_request) Successful in 3m5s
CI / mutation (pull_request) Successful in 6m7s
CI / verify-stack (pull_request) Failing after 11m42s
For a `resource: object` notification Objecten sends the object as both hoofdObject and resourceUrl — the object *is* the main resource — so `HoofdObject ?? ResourceUrl` was a branch that can never take its left side and that no test could distinguish. It came across from the zaken path, where hoofdObject genuinely differed (the zaak behind a status). Tests unchanged and green.
31 lines
1.5 KiB
C#
31 lines
1.5 KiB
C#
namespace EventSubscriber.Application;
|
|
|
|
/// <summary>
|
|
/// An inbound NRC (Open Notificaties) notification, as Open Notificaties POSTs it to an
|
|
/// abonnement callback. Only the fields the projection needs are modelled.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// Since S-19b-2 the subscriber listens on the <c>objecten</c> kanaal, not <c>zaken</c>: the
|
|
/// register record in Objecten is what the projection is derived from (ADR-0030), so the
|
|
/// projection is a cache of the register rather than a re-derivation of the case system. An
|
|
/// Objecten notification carries <b>no record data</b> — only the object URL (as both
|
|
/// <c>hoofdObject</c> and <c>resourceUrl</c>) and the objecttype as a kenmerk — so the record
|
|
/// itself is read back through the ACL.
|
|
/// </remarks>
|
|
public sealed record Notification(
|
|
string Kanaal,
|
|
string Resource,
|
|
string Actie,
|
|
Uri ResourceUrl)
|
|
{
|
|
/// <summary>A register record written to Objecten — <c>create</c> on submit, <c>update</c> on
|
|
/// approval, since the ACL upserts the same object for a registration (§8.6).</summary>
|
|
public bool IsRegisterRecordWritten =>
|
|
Kanaal == "objecten" && Resource == "object" && Actie is "create" or "update";
|
|
|
|
/// <summary>The object holding the register record. For a <c>resource: object</c> notification
|
|
/// Objecten sends the object as both <c>hoofdObject</c> and <c>resourceUrl</c> — the object is
|
|
/// the main resource — so the notification's own <c>hoofdObject</c> is not modelled.</summary>
|
|
public Uri ObjectUrl => ResourceUrl;
|
|
}
|