-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(elements): Introduce exampleMode prop on Root components #3184
Conversation
🦋 Changeset detectedLatest commit: 7bf0ed7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types 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 |
const evt: SignUpRouterInitEvent = { | ||
type: 'INIT', | ||
clerk, | ||
router, | ||
signInPath: SIGN_IN_DEFAULT_BASE_PATH, | ||
exampleMode, | ||
}; | ||
|
||
if (ref.getSnapshot().can(evt)) { | ||
ref.send(evt); | ||
} | ||
}, [clerk, router]); | ||
if (ref.getSnapshot().can(evt)) { | ||
ref.send(evt); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It made more sense to just put the init
event inside the loaded callback, instead of introducing the new event. This fixed a bug where the init event wasn't applying if clerk loaded first.
Description
Introduce
exampleMode
, which unconditionally renders the start step. In the future, we can leverage this to make "mock" functional flows in docs. We'll use this currently in the docs to showcase pre-built examples.Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change