Closed ndureiss closed 2 years ago
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/pchatard/giftlist/4GZSqX61eDGXSRqdvbsyvF4yWooi
✅ Preview: https://giftlist-git-addauth0idlist-pchatard.vercel.app
@pchatard this PR is bringing breaking changes. If it's OK from your side please take into account it needed Auth0 Actions changes (for user creation) and a DB schema reset (I choose to not create a migration file so far we are not in production mode yet).
I can lead these two actions just merging this PR.
Looks perfect for now! For arrays manipulating user objects (ex: ownerIds, grantedUsersIds, friends, etc), will it be possible to return an object composed of our new id and the display name ?
Looks perfect for now! For arrays manipulating user objects (ex: ownerIds, grantedUsersIds, friends, etc), will it be possible to return an object composed of our new id and the display name ?
I'll merge like that. I think we need to talk about this in a dedicated topic
@pchatard this PR as a proposal to fix #60, #62 and #74.
It:
description
string field to List;id
from Auth0 ones:id
prop of User is now an UUID;auth0Id
prop is created in User, all DBfind
,update
, etc. are conditionned bywhere: { auth0Id: request.userId }
clause;ownersIds
andgrantedUsersIds
are array of User id prop, in consequences neither User mail nor User Auth0 ID are exposed.