Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
🟡 Changes recommended
The documentation must state the runtime’s upper bound of 2 ** 31 - 1 for numeric path segments to avoid promising inputs the API rejects.
1 open issue
What changed in this PR
Documents upcoming JSON path filtering support in ZQL and regenerates the search index for the new guidance.
Changes:
- Adds JSON path filter syntax, traversal rules, type-strict comparisons,
IN/NOT IN, and missing/null semantics to the ZQL guide. - Regenerates searchable ZQL page and section entries.
- Keeps the documentation release-gated until Zero 1.12 ships the feature.
| File | Description |
|---|---|
| contents/docs/zql.mdx | Adds a JSON Filters section under the ZQL Where documentation covering path traversal, typed comparisons, membership filters, and missing or null values. |
| assets/search-index.json | Regenerates searchable page content and section metadata for the new JSON filter documentation. |
Review effort: Lite
| cmp(json('metadata', 'tags', 0), 'bug') | ||
| ``` | ||
|
|
||
| Array indexes must be non-negative integers. A string never indexes an array and a number never reads an object key, so `json('metadata', 'tags', '0')` reads as a missing value (see [Missing Values](#missing-values)). |
Contributor
Author
|
Superseded by #335, which merged the same |
This branch was successfully deployed
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
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.

Do not merge before Zero 1.12 is released. JSON path filters are not in a released Zero version yet. Keep this a draft until then.
Re-lands #327, which merged too early and was reverted in #330. The change to
contents/docs/zql.mdxis identical to #327.Adds a JSON Filters section to the ZQL page, under Where. It covers:
json(column, ...path)inside acmp()callback.IN/NOT INlists.null, both found withIS/IS NOT.Also regenerates
assets/search-index.json. It will conflict in that file with the aggregates docs PR; whichever lands second needs the index regenerated.