Document the `meta` query parameter
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- graphql, typescript
- Domain
- documentation
Research direction
Start with content/guides/04.connect/3.query-parameters.md and follow the existing query-parameter section format. Read sanitizeMeta in api/src/utils/sanitize-query.ts and MetaService.getMetaForQuery in api/src/services/meta.ts, then document the REST and SDK forms, explain the supported values, and note the GraphQL alternative. Update the frontmatter description to include all documented parameters, including meta.
Written by the indexing model from the issue text.
Description
Background
content/guides/04.connect/3.query-parameters.md documents every other query parameter (fields, filter, search, sort, limit, offset, page, aggregate, groupBy, deep, alias, export, version, versionRaw, functions, backlink) with its own ## section, but meta has no section and isn't mentioned anywhere on the page or elsewhere in this repo.
meta was previously proposed for deprecation in favor of aggregation (directus/directus#15665), but that was closed as not planned in 2024 ("Not dropping it, it's too popular!"). It remains fully supported today.
Scope
Add a ## Meta section to content/guides/04.connect/3.query-parameters.md, following the existing section format (description, ::code-group with REST/GraphQL/SDK tabs where applicable, any relevant ::callout).
Content notes
Source: api/src/utils/sanitize-query.ts (sanitizeMeta), api/src/services/meta.ts (MetaService.getMetaForQuery) in directus/directus.
- Accepts
total_count,filter_count, a comma-separated combination of the two, or*for both. total_count: total number of items in the collection, ignoring any filters.filter_count: number of items matching the current filter/search.- No GraphQL equivalent: GraphQL exposes counts through the separate
<collection>_aggregatedquery type instead of ametaargument, so this section likely only needs REST + SDK tabs.
Also noticed
The page's frontmatter description field lists fields, filter, search, sort, limit, offset, page, aggregate, groupBy, deep, alias, and export - missing version, versionRaw, functions, and backlink (which already have sections), as well as meta. Worth updating in the same PR since it's the same file.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 82
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from directus/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
-
content-missing
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·