Skip to content

feat: API specs update for version latest#70

Merged
ChiragAgg5k merged 1 commit into
mainfrom
feat-latest-specs
May 27, 2026
Merged

feat: API specs update for version latest#70
ChiragAgg5k merged 1 commit into
mainfrom
feat-latest-specs

Conversation

@appwrite-specs
Copy link
Copy Markdown

This PR contains API specification updates for version latest.

@ChiragAgg5k ChiragAgg5k merged commit 9aae553 into main May 27, 2026
2 checks passed
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 27, 2026

Greptile Summary

This automated bot PR makes two categories of changes across all five API spec files: it adds x-enum-keys metadata to enums throughout the specs, and it repositions presencelogs/presence_logs earlier in the audit-log resource-type enum in console specs.

  • x-enum-keys additions: Populates the previously-missing x-enum-keys field on dozens of enums (e.g., OAuthProvider, AuthenticationFactor, Timezone, BrowserTheme, RedirectStatusCode, ProjectUsageRange). For string-valued enums the keys mirror the enum values directly; for numeric-coded enums (e.g., HTTP redirect status codes) human-readable aliases are provided (MovedPermanently, Found, etc.), consistent with code-generator conventions used elsewhere in the spec.
  • presencelogs reordering: Moves presencelogs and presence_logs from their previous position (after transactionlogs) to after targets in the audit-log resource-type parameter. The change is applied consistently across all console spec files (OpenAPI3 and Swagger2); server and client specs are unaffected as expected since this parameter is console-only.

Confidence Score: 5/5

All changes are additive metadata (x-enum-keys) or enum value reorderings with no impact on wire-format validation; safe to merge.

The diff is entirely generated spec metadata — no logic, no runtime code, no schema type changes. x-enum-keys is an additive extension field that code generators consume; its absence would merely produce less readable constant names, not breakage. The presencelogs reordering affects only the display order of an enum, and the change is applied consistently across every relevant spec file.

No files require special attention.

Important Files Changed

Filename Overview
specs/latest/open-api3-latest-console.json Moves presencelogs/presence_logs earlier in the audit-log resource-type enum (after targets instead of after transactionlogs) and adds x-enum-keys to ProjectUsageRange and RedirectStatusCode.
specs/latest/open-api3-latest-server.json Adds x-enum-keys to the RedirectStatusCode enum with human-readable names (MovedPermanently, Found, TemporaryRedirect, PermanentRedirect) for the four supported redirect status codes.
specs/latest/swagger2-latest-client.json Adds x-enum-keys to several enums including AuthenticatorType, AuthenticationFactor, and OAuthProvider; no structural changes.
specs/latest/swagger2-latest-console.json Largest file in the diff — adds x-enum-keys across many enums (OAuthProvider, Timezone, BrowserTheme, etc.) and mirrors the presencelogs/presence_logs reordering from the OpenAPI3 console spec.
specs/latest/swagger2-latest-server.json Adds x-enum-keys to AuthenticatorType, AuthenticationFactor, OAuthProvider, BrowserTheme, Timezone, and related enums; no presencelogs reordering (expected, as that audit-log parameter is console-only).

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

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