Fix Invite Acceptance Page

[JamesonRGrieve]

• Register button should be "Accept Invitation"
• Half-complete sentence in description.
• Should set the auth-team cookie based on the invitation ID and retrieve and render the name.

[jnelsoncelsys]

@waiscodes please review the following triage content:

User Story:

As a new user invited to the platform,
I want the invite acceptance page to clearly reflect the invitation context,
So that I understand I'm accepting an invite and the experience feels personalized and complete.
—

Acceptance Criteria (Checklist):

[ ] The "Register" button should be renamed to "Accept Invitation"

[ ] The description text on the page should be complete and grammatically correct

[Sub-detail A] Ensure no placeholder or incomplete sentences are shown

[Sub-detail B] Text should clearly explain the invitation process

[ ] The auth-team cookie should be set based on the invitation ID

[Sub-detail A] Retrieve the team name associated with the invitation

[Sub-detail B] Render the team name on the page for user context
—

Suggested Implementation Notes:

Component/Area: pages/invite/[inviteId].tsx

Update the button label from "Register" to "Accept Invitation"

Review and fix the description text block for completeness

Use getServerSideProps or useEffect to fetch invitation details using the inviteId param

Set the auth-team cookie using setCookie from nookies or similar utility

Component/Area: lib/invitations.ts

Add or update a function to fetch invitation details (e.g., team name) by inviteId

Component/Area: components/InviteAcceptance.tsx (if exists)

Ensure props include team name and are rendered appropriately
—

Dependencies:

API Call: lib/invitations.ts // Fetch invitation details by ID

Cookie Utility: node_modules/nookies or utils/cookies.ts // For setting auth-team cookie

Page Route: pages/invite/[inviteId].tsx // Main invite acceptance page
—

Time Estimate:
4–6 hours

—

Additional Notes:

Ensure that the auth-team cookie is scoped correctly (e.g., path, expiration) to be available for downstream pages.

Consider adding a loading state while fetching invitation details.

Validate that the invite ID is valid and handle error states gracefully (e.g., expired or invalid invite).

[waiscodes]

This is currently blocked on the api for invitations so I created a sub-issue to separate just the UI work and this can be completed as soon as the api is ready

[jnelsoncelsys]

@waiscodes and @JamesonRGrieve we will peer review 29, and leave 11 (this issue) partially blocked.

[jnelsoncelsys]

@waiscodes and @JamesonRGrieve peer review was successfull, and we need to merge this if approved on your end.