Loading
fix(037): entity-id discovery semantics, GeoJSON polygon, three-page pagination
037_10_01 queried /csourceRegistrations with REGISTRATION ids in ?id=,
but the parameter is a 'List of entity ids to be retrieved' — it
filters by what the registrations' EntityInfos can provide. The test
now queries two Building entity ids: the second and third registrations
(type Building, no id constraint) can provide them, the first one
(Vehicle:A456 pinned + OffStreetParking id patterns) cannot and is
excluded. The expected ids were also passed comma-joined into the
keyword's @{varargs} (one element); now separate arguments.
Both 037-10 expectation files are rebuilt from the actual fixtures —
they carried a 'location' member the csourceProperty fixture never had.
037_07_02's polygon was not valid GeoJSON (RFC 7946): single ring at
the wrong nesting level and not closed. Now [[[...,first==last]]], the
same shape its passing siblings use.
037_11 assumed three type=Building registrations but its first fixture
registers Vehicle/OffStreetParking only — 037_11_01/02 expected a third
page that never existed (and _01's next-link pointed at
/csourceSubscriptions, a copy-paste slip; offset=2 of three matches is
the last page, so no next link per clause 5.5.9). First fixture is now
a Building one and _03 expects all three.
Analysis recorded as testsuite-doubts.md #98.