Keep the released parameter order for updateOAuth2Kakao · Issue #14498 · appwrite/appwrite · GitHub
Skip to content

Keep the released parameter order for updateOAuth2Kakao #14498

Open

Description

@ChiragAgg5k

Tracks PR #14497.

Plan

Goal: Keep project.updateOAuth2Kakao in its released SDK parameter order (clientId, clientSecret, prompt, enabled). #14467 moved prompt after enabled for every provider on the OAuth2 Base path, so the next SDK regeneration would shift existing positional Kakao calls.

What changes:

  • src/Appwrite/Platform/Modules/Project/Http/Project/OAuth2/Base.php: new isPromptBeforeEnabled() hook (defaults to false). When a provider returns true, prompt is declared before enabled and the route uses a new updateWithPromptFirst() callback that forwards to updateWithPrompt() with the arguments in the right order.
  • src/Appwrite/Platform/Modules/Project/Http/Project/OAuth2/Kakao/Update.php: overrides isPromptBeforeEnabled() to return true.
  • app/config/sdks/parameters.lock.json: both project.updateOAuth2Kakao entries record prompt before enabled.
  • Other providers keep their current order: Discord, GitHub and Zoho stay clientId, clientSecret, enabled, prompt, and Amazon (no prompt) stays clientId, clientSecret, enabled.

Remaining steps: None. The linked PR is the full change.

Done when:

Activity

  1. self-assigned this
    on Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

product / messagingFixes and upgrades for the Appwrite Messaging.sdk / cliFixes and upgrades for the Appwrite CLI.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions