dunglas / mercure / 29919598305

88%

master: 93%

push

github

feat!: carry subscription API cursor in the rel="mercure" Link header (#1307)

* feat!: carry subscription API cursor in the rel="mercure" Link header

The reconciliation cursor was exposed two ways: a last-event-id Link
attribute at discovery, and a last_event_id JSON body property on the
subscription API. Unify on the Link header the API already advertises, so
a single-subscription response body is exactly the subscription event
document. The hub now also exposes the Link header via CORS so cross-origin
subscribers can read it.

BREAKING CHANGE: the subscription API no longer returns the last_event_id
JSON property; read the last-event-id attribute of the rel="mercure" Link
response header instead.

* feat: advertise SSE type and content-type on the rel="mercure" Link header

Discovery gains an optional `type` attribute naming the SSE event type
updates will carry, so a native EventSource client can register the right
listener at bootstrap instead of silently dropping named events. Keep
`content-type` (it fills the gap that SSE data fields carry no content type,
avoiding sniffing). Both are single-valued hints and MUST be omitted for
heterogeneous streams; routing stays governed by topic matchers.

The hub now also sets these on the subscription API Link header, where the
stream is homogeneous by definition (reserved "mercure" type, JSON body).

* docs: refine subscription API and discovery wording for RFC style

* fix: drop unused initSubscription return and wrap long JS line for CI

* docs: inline the single-item last-event-id bullet as prose

26 of 35 new or added lines in 3 files covered. (74.29%)

2786 of 3257 relevant lines covered (85.54%)

113.34 hits per line