You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expose additionalData in SignUp and SignIn render props - #119
A consumer that renders sign-up or sign-in through render props (React children function / Vue default scoped slot) has no way to read the current step's additionalData. The default UI already uses it (e.g. source lookups for KEY_VALUE_LIST, such as account-linking prompts), but custom UIs like a SignUpBox can't. This exposes it in both sign-up and sign-in so the two stay consistent. Nuxt re-uses the Vue component and forwards its slot; the Next.js SignUp now forwards children to BaseSignUp so Next.js consumers can use render props too.
Approach
Add additionalData: Record<string, unknown> to BaseSignUpRenderProps and BaseSignInRenderProps in React and Vue. Sign-up reads it from the current flow step's data.additionalData; sign-in passes through its existing additionalData prop.
Default it to {} (as SignIn and BaseAcceptInvite already do), so consumers don't need a null check.
This pull request is labelled parity/prs-not-needed: nothing here has to ship in the other ThunderID SDKs. If that changes, swap the label for parity/prs-raised.
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
📝 Walkthrough
React and Vue sign-in and sign-up render APIs expose additionalData from the current flow. Tests verify that render-prop children and scoped slots receive the data. Next.js SignIn accepts children, and Next.js SignUp renders children inside BaseSignUp.
React and Vue sign-in and sign-up render APIs include additionalData in their render props. Sign-up passes the current flow data, defaulting to an empty object when absent. Tests verify that sign-in and sign-up data reaches render-prop children and scoped slots.
Accept and render Next.js children packages/nextjs/src/client/components/presentation/SignIn/SignIn.tsx, packages/nextjs/src/client/components/presentation/SignUp/SignUp.tsx
Next.js SignIn accepts children. Next.js SignUp renders its children inside BaseSignUp.
The supplied evidence shows the new data reaches Next.js render-prop consumers. No actionable merge-blocking risk remains after normal checks.
Pre-merge checks: 5
Check name
Status
Explanation
Description check
The description clearly states the purpose, implementation approach, related work, testing status, parity status, and security checks. Manual testing, documentation, and integration tests are not mark…
Title check
The title clearly and concisely identifies the main change: exposing additionalData in SignUp and SignIn render props.
Docstring Coverage
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Some tools did not complete. Review the errors below.
🔧 ESLint
If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.
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
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.
Purpose
A consumer that renders sign-up or sign-in through render props (React
childrenfunction / Vue default scoped slot) has no way to read the current step'sadditionalData. The default UI already uses it (e.g.sourcelookups forKEY_VALUE_LIST, such as account-linking prompts), but custom UIs like aSignUpBoxcan't. This exposes it in both sign-up and sign-in so the two stay consistent. Nuxt re-uses the Vue component and forwards its slot; the Next.jsSignUpnow forwardschildrentoBaseSignUpso Next.js consumers can use render props too.Approach
additionalData: Record<string, unknown>toBaseSignUpRenderPropsandBaseSignInRenderPropsin React and Vue. Sign-up reads it from the current flow step'sdata.additionalData; sign-in passes through its existingadditionalDataprop.{}(asSignInandBaseAcceptInvitealready do), so consumers don't need a null check.childrenin the Next.jsSignUp.Related Issues
Related PRs
SignUpBoxneeds this to renderKEY_VALUE_LIST,COPYABLE_TEXTandQR_CODEin sign-up flows)Checklist
breaking changelabel added.parity/prs-raisedorparity/prs-not-neededadded.parity/prs-raised, the port links are posted as a reply on the parity check's comment.Security checks
Summary by CodeRabbit