Per-reference label sources for the search-as-pipeline design (epic: #534). Largely independent of the pipeline core change.
Scope
- Generalize the single
labelsCollection option -> a per-reference label source: each reference declares which collection resolves its label (and optionally more fields). A labels collection and a typed entity collection are the same kind of thing.
- Batched query-time label resolver; pruned by GraphQL field selection; degrades gracefully on dangling references.
- Local label denormalized on the doc (within-source); canonical label via an opt-in nested field resolved query-time (clients never join).
Acceptance
- Unit: references resolve labels from their configured source, batched; a dangling reference resolves to a graceful fallback; a non-selected reference field is not resolved.
Design and rationale: #534.
Per-reference label sources for the search-as-pipeline design (epic: #534). Largely independent of the pipeline core change.
Scope
labelsCollectionoption -> a per-reference label source: each reference declares which collection resolves its label (and optionally more fields). A labels collection and a typed entity collection are the same kind of thing.Acceptance
Design and rationale: #534.