docs: add query conditions reference to programmatic-table-requests skill#34
Conversation
The skill only documented URL/FIQL query string syntax. Agents writing custom resources had no reference for the programmatic conditions API, including the exact comparator strings (equals, greater_than, etc.) which differ from the FIQL equivalents and are critical for queries to work at all. Adds a full reference for the conditions object shape, all comparator values, query object parameters, and annotated examples covering common patterns (simple filter, AND+OR, relationship traversal, sort+paginate). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Conditions/comparators are only relevant when using the JS table API (search, get, subscribe) — not URL queries. Moved the full conditions reference (shape, comparator table, query params, examples) to programmatic-table-requests.md and restored querying-rest-apis.md to URL/FIQL-only content. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Ethan-Arrowood
changed the title
| | `less_than` | `<` | | ||
| | `less_than_equal` | `<=` | | ||
| | `starts_with` | String starts with value | | ||
| | `contains` | String contains value | |
There was a problem hiding this comment.
@kriszyp which ones do we want to flag as dangerous from a performance perspective?
There was a problem hiding this comment.
contains and ends_with are the ones that defeat any indexing.
kriszyp
left a comment
kriszyp
left a comment
There was a problem hiding this comment.
You can merge, but this still falls into the category of things that I think the skills should really be pulling from documentation. I think @dawsontoth has been looking into a strategy for doing this in way that would allow us to really have the documentation be the canonical source of, well... documentation.
| | `less_than` | `<` | | ||
| | `less_than_equal` | `<=` | | ||
| | `starts_with` | String starts with value | | ||
| | `contains` | String contains value | |
There was a problem hiding this comment.
contains and ends_with are the ones that defeat any indexing.
|
🎉 This PR is included in version 1.4.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
3 participants
Summary
programmatic-table-requests.md— the right home since conditions are only relevant when using the JS table API (search(),get(),subscribe()) inside custom resourcesconditionsarray shape (attribute,value,comparator,operator, nestedconditions)equals,not_equal,greater_than,greater_than_equal,less_than,less_than_equal,starts_with,contains,ends_with,between) — these differ from URL/FIQL syntax and must be exactlimit,offset,select,sort)querying-rest-apis.mdis unchanged (URL/FIQL syntax only)Motivation
An agent failed to build working queries inside a custom resource because there was no reference for the programmatic conditions API. The comparator names (
equals,greater_than, etc.) differ from URL/FIQL equivalents (eq,gt) and incorrect names silently fail.Test plan
search()streaming pattern🤖 Generated with Claude Code