Reschedule cancels the session in one click, with no confirmation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- next.js, postgresql, typescript
- Domain
- frontend, full-stack
Research direction
Start at the session page and inspect the existing inline confirmation used by Cancel, then compare the Reschedule flow. Add the confirmation text and the two choices from the issue before cancellation proceeds. Check that keeping the session leaves it unchanged and confirming continues to pick a new time; the issue names page.tsx for the related mentor visibility work, which RFC-0007 should address.
Written by the indexing model from the issue text.
Description
Found in the UX review of the calendar work (RFC-0012). On the session page, Reschedule immediately cancels the session, emails the partner a cancellation, and — with calendar sync — deletes both calendar events and the Meet link, before the mentee has picked a new time. If they don't rebook, the session is simply gone.
Until proper rescheduling (RFC-0007) lands, add the same inline confirmation that Cancel uses:
Reschedule this session?
This cancels the current time — {partner} is told and it's removed from both calendars — then you pick a new time.
[Cancel and pick a new time] [Keep session]
Also: mentors never see Reschedule (page.tsx), which RFC-0007 should cover.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 6
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 56
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from grasshopper-protocol/grsshppr
-
Add tests for utils.ts cn() functionPossibly taken @yogesh201sits claimed this 6 days ago. Opengood first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
grasshopper-protocol/grsshppr#81 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
code quality documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
grasshopper-protocol/grsshppr#78 ·
Maintainers usually reply within 1 day
-
a11y documentation good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
grasshopper-protocol/grsshppr#77 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
grasshopper-protocol/grsshppr#46 ·
Maintainers usually reply within 1 day
-
Adopt the Separator primitive for ad-hoc dividersPossibly taken @yogesh201sits claimed this 6 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
grasshopper-protocol/grsshppr#45 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in grasshopper-protocol/grsshppr
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
keptinventory/kept#336 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
hemi-earn
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vetro-protocol/vetro-monorepo#1013 ·
Maintainers usually reply within 1 day