Skip to content

Conversation

subhankarmaiti
Copy link
Contributor

This PR updates the documentation to improve clarity and accuracy around directing users to the login or signup screens using the screen_hint parameter.

Changes Included

  • EXAMPLES.md

    • Wrapped login_hint and screen_hint inside the additionalParameters object, as required by the SDK.
  • FAQ.md

    • Added a new question: "How can I prompt users to the login page versus signup page?"
    • Included sample login and signup functions using the correct usage of screen_hint inside authorize().

Why This Change?

  • Clarifies a frequently asked use case—how to route users to specific authentication screens.
  • Fixes potential confusion around parameter placement in authorize() options.
  • Ensures documentation reflects the current SDK behavior.

Related Resources

@subhankarmaiti subhankarmaiti requested a review from a team as a code owner July 24, 2025 08:09
@subhankarmaiti subhankarmaiti merged commit e6e4b17 into master Jul 24, 2025
3 checks passed
@subhankarmaiti subhankarmaiti deleted the faq_update branch July 24, 2025 08:46
@subhankarmaiti subhankarmaiti mentioned this pull request Oct 1, 2025
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.

2 participants