fix(docs): correct aggreagteOrder typo in GraphQL guide - #206
Merged
Conversation
jackchuka
force-pushed
the
fix/aggregate-order-typo
branch
from
August 13, 2026 02:54
0214533 to
ac8083c
Compare
jackchuka
marked this pull request as ready for review
August 13, 2026 02:55
anukiransolur
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects
aggreagteOrder→aggregateOrderindocs/getting-started/graphql.md(lines 338 and 349).Why
The platform's generated aggregation query is
aggregate<TableName>, and the same section spells it correctly for the sibling example (aggregateProduct, lines 322 and 330).aggreagteOrderis not a real API name, so anyone copy-pasting the GraphQL snippet gets an unknown-field error.How it was found
Renovate PR #194 bumps
crate-ci/typosv1.48.0 → v1.49.0, and itstypo-checkjob fails on exactly this word, twice. The v1.49.0 dictionary added theaggreagtemisspelling family:v1.48.0 only carried the different
aggreagatefamily (extraa), which is why the existing content passed until now.Sequencing
The typo is on
main, not on the Renovate branch, so this needs to land first — then #194 can be rebased and will go green. If #194 merges before this, every subsequent PR in the repo will failtypo-checkuntil this lands.Deliberately not allowlisting the word in
_typos.toml: the detection is correct, and suppressing it would leave a broken code sample in the published docs.