Closed HectorAgudelo closed 1 week ago
Touched base with @HectorAgudelo, the InviteRevokeStore.ts
was initially intended to maintain some state. Over time the implementation had changed to not require state, so we will merge as-is with the intent of cleaning this up into the existing route-handler endpoint for referralInvite
or refactoring into the same userData
endpoint that currently houses the user's invite data.
@HectorAgudelo @pm-moyanor The code looks great and core functionality is there which is awesome -- nice work!
There is one area that I'm confused about.
inviteRevokeAction
(defined insideInviteRevokeStore.ts
) is currently a Jotai atom that makes a POST request toe thereferralInvite
endpoint. What is the thinking behind turning this into an atom instead of creating an API route handler as we have for other POST requests?