Skip to content

feat: API specs update for version 1.9.x#69

Merged
ChiragAgg5k merged 1 commit into
mainfrom
feat-1.9.x-specs
May 27, 2026
Merged

feat: API specs update for version 1.9.x#69
ChiragAgg5k merged 1 commit into
mainfrom
feat-1.9.x-specs

Conversation

@appwrite-specs
Copy link
Copy Markdown

This PR contains API specification updates for version 1.9.x.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 27, 2026

Greptile Summary

This auto-generated PR adds x-enum-keys metadata arrays alongside existing x-enum-name fields across all swagger2 specs, and corrects the ordering of presencelogs/presence_logs in the OpenAPI 3 console spec to match the swagger2 console spec. The server spec also re-orders the /storage/buckets/{bucketId} path block so it appears directly after /storage/buckets in the JSON object, which is a cosmetic restructuring with no functional effect.

  • x-enum-keys additions are consistently applied only to request-parameter enums; response-definition enums (AttributeStatus, ColumnStatus, etc.) are intentionally left without keys, matching the established pattern.
  • The presencelogs reordering in open-api3-1.9.x-console.json aligns the enum position with the swagger2-1.9.x-console.json spec.
  • In swagger2-1.9.x-client.json the x-enum-name and x-enum-keys counts are an exact 1:1 match (16 each), confirming no enums were missed or double-counted.

Confidence Score: 5/5

All changes are additive metadata fields and cosmetic re-orderings with no behavioral impact on any API endpoint.

Every modified spec file receives consistent, mechanically applied x-enum-keys additions that mirror existing enum arrays. The only structural change (storage bucket path re-ordering in the server spec) is semantically neutral. No endpoints, parameters, response schemas, or auth scopes are altered.

No files require special attention; all changes are machine-generated and internally consistent.

Important Files Changed

Filename Overview
specs/1.9.x/open-api3-1.9.x-console.json Reorders presencelogs/presence_logs enum values to appear before companies instead of after transactionlogs, aligning with the ordering already used in the swagger2 console spec.
specs/1.9.x/swagger2-1.9.x-client.json Adds x-enum-keys arrays alongside all existing x-enum-name fields for every request parameter enum (AuthenticatorType, AuthenticationFactor, OAuthProvider, BrowserTheme, Timezone, BrowserPermission, ImageFormat, ImageGravity, ExecutionMethod); counts match perfectly (16 x-enum-name = 16 x-enum-keys).
specs/1.9.x/swagger2-1.9.x-console.json Adds x-enum-keys to all request-parameter enums (AccountKeyScopes, AuthenticatorType, AuthenticationFactor, OAuthProvider, BrowserTheme, Timezone, and others); response-definition enums (AttributeStatus) are intentionally left without x-enum-keys.
specs/1.9.x/swagger2-1.9.x-server.json Adds x-enum-keys to request-parameter enums and re-orders /storage/buckets/{bucketId} path to appear directly after /storage/buckets in the JSON object (functionally equivalent; response-definition enums like AttributeStatus/ColumnStatus are intentionally unchanged).

Reviews (1): Last reviewed commit: "chore: update API specs and SDK examples" | Re-trigger Greptile

@appwrite-specs appwrite-specs Bot force-pushed the feat-1.9.x-specs branch from 98da1b5 to 4d045d0 Compare May 27, 2026 07:24
@ChiragAgg5k ChiragAgg5k merged commit e7ad1dc into main May 27, 2026
1 check passed
@ChiragAgg5k ChiragAgg5k deleted the feat-1.9.x-specs branch May 27, 2026 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant