Implement receiving-side logic for suggestions #2
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
foravo/milestone-proof-20260519050317#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub issue
StanfordCS194/spr26-Team-22#100.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/100
Original author: @nriedman
Original state: open
Summary
Right now, multi-user interactions are simplified by having the receiver of the invitation be simulated as instantly accepting. Instead, we need to implement the full invitation pipeline that will allow a user to accept or decline incoming invitations.
Notes
Not sure if we'll be able to get to this one.
Imported from GitHub issue comment
StanfordCS194/spr26-Team-22#100:4458620237.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/100#issuecomment-4458620237
Original author: @yusabd
For this, we are currently using Supabase, but did not finish debugging it.