Repository navigation
feat(backend): add API to leave hackathon - #397
Merged
Merged
Conversation
sabinem
added a commit
that referenced
this pull request
Nov 6, 2026
A confirmed participant leaves from their own profile inside the hackathon. Somebody still on the waitlist cancels from the public page, the only page they can open. Both call the Leave RPC (#397) through one helper, and both ask first in the app's confirm dialog, which gains an optional cancelLabel so "Cancel registration" does not sit beside a bare "Cancel". Leave is not offered to owners: the RPC keeps the Owner role, so they would still run the hackathon. Nor once it has finished, which the RPC refuses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Leavehandler that lets users leave a hackathon they are member of.Even though the issue mentions adding a new
Participantservice, I addedLeavein theHackathonservice. I believe it makes more sense there, as other similar actions (e.g. Join) are there as well. If we decide that we want to add a newParticipantservice, all these actions should be moved as well, creating a change in the API. This would require a PR on its own.Related issue: #346
Note
Because it was not mentioned in the issue I took the following decisions:
Let me know if you think something is wrong and should behave differently.