Repository navigation
feat: profile fields on /register (@profullstack/profile) - #108
Merged
Merged
Conversation
/register now asks for first and last name (required) plus company domain, job title and LinkedIn (optional) with the shared @profullstack/profile 0.1.3 component. POST /api/auth/signup-profile validates them on the server before supabase.auth.signUp, then stores them for the new, still unconfirmed account (same address, created in the last 15 minutes, no profile yet). The fields also ride in signUp user metadata and are saved on /auth/callback if that call never lands. GET/PUT/PATCH /api/v1/me/profile plus a Profile card on /settings. Stored in a new server-only user_profiles table (RLS on, no anon or authenticated policies). contacts.company is CRM data and is untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan12 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 4 | LOW: 6
Snippets are redacted; ThreatCrush never prints matched credential material. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
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.
Adopts the shared
@profullstack/profile(0.1.3, exact) on smshub.dev.ProfileFieldsfor first/last name (required), company domain, job title, LinkedIn (optional), styled like the existing inputs.validateProfilebefore the clientsupabase.auth.signUp; after signUp it stores the fields for the new account only if it is unconfirmed, created < 15 min ago, same address, and has no profile yet. Stand-in users (identities: [], existing address) are skipped.options.datacarries the normalized fields;/auth/callbacksaves them if there is still no profile row (never blocks sign-in).GET/PUT/PATCH /api/v1/me/profile; /settings gets a Profile card (GET prefill, PATCH save).supabase/migrations/016_user_profiles.sql, the package's own table keyed by auth user id, RLS on with no anon/authenticated policies. Applied by hand to dev2smshub-dev-supabase-db.contacts.company(CRM data) untouched. No backfill (no account-holder name column).src/app/api/__tests__/signup-profile.test.ts. typecheck, lint, 306 tests pass.🤖 Generated with Claude Code