Background
Follow-up to #32 (Fetching Records Using a Query — CLOSED). A gap review of openapi.yaml against the CloudKit JS query request (cloudkitjs.md:1822-1840) and the Web Services reference found the records/query request body is missing two documented options.
Current state
records/query request body (openapi.yaml:51-67) exposes only: zoneID, resultsLimit, query, desiredKeys, continuationMarker.
What needs to be done
Add to the request body schema:
zoneWide (boolean) — query across all zones rather than a single zone.numbersAsStrings (boolean) — return numeric field values as strings (avoids JS precision loss; relevant for INT64).
Implementation notes
- Edit
openapi.yaml only, then regenerate via ./Scripts/generate-openapi.sh. Never hand-edit Sources/MistKitOpenAPI/.
- Surface the new options through the relevant
CloudKitService query method(s).
Background
Follow-up to #32 (Fetching Records Using a Query — CLOSED). A gap review of
openapi.yamlagainst the CloudKit JS query request (cloudkitjs.md:1822-1840) and the Web Services reference found therecords/queryrequest body is missing two documented options.Current state
records/queryrequest body (openapi.yaml:51-67) exposes only:zoneID,resultsLimit,query,desiredKeys,continuationMarker.What needs to be done
Add to the request body schema:
zoneWide(boolean) — query across all zones rather than a single zone.numbersAsStrings(boolean) — return numeric field values as strings (avoids JS precision loss; relevant forINT64).Implementation notes
openapi.yamlonly, then regenerate via./Scripts/generate-openapi.sh. Never hand-editSources/MistKitOpenAPI/.CloudKitServicequery method(s).