Skip to content

docs(error-catalog): INVALID_FIELD names the refusal of a search over an empty resolved search set #24353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 1 commit into from
Oct 18, 2026
+4 −0
Merged

docs(error-catalog): INVALID_FIELD names the refusal of a search over an empty resolved search set #24353

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/docs/api/error-catalog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,6 +159,10 @@ aggregation's own `filter`), a sort, a `groupBy`, an `aggregations[].field`, a
`searchFields` entry, or an `expand` entry's own filter or sort at any depth. Such a
field is never returned on a generic read, so it cannot be queried by either — the
refusal names the object that declares it. Query by another field.
A non-blank `search` is refused (`param: 'search'`), not answered with every row,
when the object's resolved search set is empty: no `searchableFields` entry names a
stored field, and the default search scans none (`internal: true` fields never
count). Declare one that does, or mirror a composed title onto a stored text field.
Off the request path the same code answers `backfillSummaryNulls`'s
`recomputeUndefinedOnEmpty` (`os migrate summary-nulls
--recompute-undefined-on-empty object.field`) when an entry is not a roll-up
Expand Down
Loading