feat(nextjs): Mark keyless onboarding as complete when stored keys match explicit keys #4971
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tch explicit keys
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 2578096 The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…loper-has-explicitly-set-the
panteliselef
commented
Jan 24, 2025
…loper-has-explicitly-set-the
brkalow
approved these changes
Jan 28, 2025
panteliselef
deleted the
elef/actls-68-notify-dashboard-that-the-developer-has-explicitly-set-the
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Calling
completeAccountlessApplicationOnboardingwill notify the dashboard to automatically proceed from step 2, to step 3 on the claim flow.Since this is called inside
ClerkProvider, we can to avoid making a BAPI request frequently. When the request successfully resolved, we are caching it for 24 hours, otherwise in case of an error it will be cached only for 10 minutes.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change