Fix availability/suggestion dependency #5
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#5
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#97.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/97
Original author: @nriedman
Original state: open
Summary
Right now, we cannot generate a suggestion if the user hasn't given their availability. This was a surprising behavior to users at Demo Day 2, and users didn't understand why no suggestions were available at first. We should design the availability + suggestion feature in such a way that it doesn't create a hidden dependency like this.
Requirements
Either add availability querying to the onboarding flow so that users always gives availability, add a hint in the suggestion UI indicating the suggestion is unavailable until the user gives their availability, make it so that suggestions can still be generated even without explicit availability, or some combination of the above.
Notes
N/A