Populate Next.js UserProfile fields from users/me/meta schema

[janithjay]

Purpose

<UserProfile> component in @thunderid/nextjs didn't receives a userSchema, so it always renders through BaseUserProfile's schema-less fallback path. Raw flattened profile keys were used with generic, startCase derived labels (Ou Id, Family Name, Sub) instead of the schema's configured display names, and no required/regex validation on edit.

Approach

Traced the gap through the full data path and found userSchema was dropped at three separate points, so all three needed fixing together,

• ThunderIDServerProvider (server/ThunderIDProvider.tsx) calls getUserAction (ID token claims) and getUserProfileAction (getUsersMe), but nothing ever calls getUsersMeMeta. Added ThunderIDNextClient.getUserSchema() and a new server/actions/getUserSchemaAction.ts server action, called alongside the existing two under the same shouldFetchUserProfile gate.

• The client-side provider (client/contexts/ThunderID/ThunderIDProvider.tsx) had userSchema: null hardcoded in its context value, and never received the schema as a prop in the first place. Added a userSchema prop, synced into state the same way userProfile already is, and passed it into <UserProvider userSchema={userSchema}>. The actual context useUser() reads from, which the hardcoded value never reached regardless.

• client/components/presentation/UserProfile/UserProfile.tsx only destructured {profile, flattenedProfile, onUpdateProfile, updateProfile} from useUser(), omitting userSchema entirely, and never passed it to <BaseUserProfile>. Even with the schema correctly available upstream, this component would still never have rendered it. Fixed to read and pass userSchema through.

After Fix

Related Issues

• fixes UserProfile component doesn't populate fields using schema in Next.js SDK thunderid#5041

Related PRs

• N/A

Checklist

• Followed the contribution guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Tests provided. (Add links if there are any)
  • Unit Tests
  • Integration Tests
• Breaking changes. (Fill if applicable)
  • Breaking changes section filled.
  • breaking change label added.

Security checks

• Followed secure coding standards.
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.

[coderabbitai]

Important

Review available on request

• 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 73aa0224-bc06-4626-89d4-ea7f810a1d4c

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.