feat: create OTP sign-in scenario preset#307
Open
AbuJulaybeeb wants to merge 5 commits into
Open
Conversation
Collaborator
|
Fix conflict |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What was done
Added OTPType and OTPFixture types to src/features/demo-admin-dashboard/types/otp.ts.
Created deterministic OTP and passkey demo presets in src/features/demo-admin-dashboard/fixtures/otpFixtures.ts.
Updated DashboardSection locally inside types.ts to include the new otp section.
Updated DemoAdminDashboard.tsx to include a new tab that displays the sender labels, safe codes, and message types (SMS, Email, Passkey) derived from the fixtures.
Why it was done
This fulfills part of the Demo Admin Dashboard initiative (Issue 46 of 70). It allows maintainers to easily populate demo UI fixtures involving OTP and passkeys without connecting to live data or altering existing infrastructure.
How it was verified
Verified that all changes were strictly scoped within the src/features/demo-admin-dashboard/ folder.
Verified that data is exclusively fake, deterministic, and safe for a public repository.
Reviewed that no files outside the target directory (e.g., protocol or inbox handlers) were touched.
Closes #211