Loading
fix(D011): query-forward assertions vs broker-correct behaviour
- stub URLs used attrs= for the forwarded projection; attrs is also entity SELECTION (an entity with none of the listed attributes does not match), so a broker must not forward it — split entities held partially at a source would be silently dropped. Brokers forward the projection-only pick= instead; the stubs now expect that form (D011_01_02/03/04_inc, D011_01_exc, D011_02_exc) - Query Entities Via POST sent Content-Type application/ld+json with the @context in a Link header and none in the body — illegal both ways (TS 104-176 clause 6.2.4). For ld+json the @context now goes in the body; the Link form stays for plain json - D011_02_exc: the fixture's redirectionOps group does not include queryBatch (TS 104-175 Table 9.2-2) — the POST variant now restricts the registration to the operation under test, as D011_03_inc already does - HttpCtrl POST /entityOperations/query stub matching crashed on array stub bodies (response_body['type'] on a list) and KeyError'd when the request selector carried no id; rewritten as a tolerant helper that also accepts the expanded-IRI form of a term where the stub uses the short name (the GET matcher's substring check already tolerated this)