Maurice 89f3055a29 fix(journey): one journal link per trip as a unique trip id, factories within tsc's depth ...

The link table keyed by the trip id made both entities a one-to-one, and the
test typecheck failed with TS2589 in the itinerary factory. It now holds its
own id with trip_id UNIQUE, as trip_invite_tokens does, and its members hang
off link_id.

The factory error was not this table's alone: any further relation on trips,
journeys or users tipped the same check. insertRow and createRow now take a
caller's overrides as their own argument instead of a spread checked against
RequiredEntityData, so a new relation no longer breaks the itinerary and tour
factories.

The suites that hand-build TripMembersService get a journalLinksStub.

2026-10-18 17:41:18 +02:00

..

e2e

feat(tours): a paddle tour's obstacle checklist and check bench on the server

2026-10-17 00:29:18 +00:00

fixtures

test(db): boot a v4.3.3 install with real rows on this release

2026-10-08 13:02:57 +02:00

helpers

fix(journey): one journal link per trip as a unique trip id, factories within tsc's depth

2026-10-18 17:41:18 +02:00

integration

feat(journey): a trip can link a journal and open it to the members it picks

2026-10-18 15:59:33 +02:00

unit

fix(journey): one journal link per trip as a unique trip id, factories within tsc's depth

2026-10-18 17:41:18 +02:00

websocket

style: format server and shared with prettier

2026-10-10 21:23:37 +02:00

build-schema-snapshot.ts

refactor(db): open the database through a DatabaseLifecycle provider

2026-10-08 18:38:28 +02:00

global-setup.ts

refactor(db): open the database through a DatabaseLifecycle provider

2026-10-08 18:38:28 +02:00

setup.console-noise.ts

style: format server and shared with prettier

2026-10-10 21:23:37 +02:00

setup.ts

style: format server and shared with prettier

2026-10-10 21:23:37 +02:00