spacebarchat / spacebarchat/server
[API] Route: /guilds/:id/archive
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 323
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 4
Description
Archiving a guild would freeze it as read-only to everyone including the guild owner. Can be used by the guild owner (in owned guilds) or those with server-wide MANAGE_GUILDS.
- If invoked by guild owner, guild owner can unarchive.
- If invoked by
MANAGE_GUILDSorOPERATORfrom outside that guild,OPERATORcan unarchive.
To archive, send a PUT request to the endpoint. To unarchive, send a DELETE request.
An archived guild has all its mass invites invalidated but users previously joined by those not kicked. User-specific invites remain valid but unusable until unarchived.
Contributor 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.
Research direction
Start at the /guilds/:id/archive API entry point and review the existing guild permission and invite-handling paths. Implement the specified PUT archive and DELETE unarchive behavior, including owner, MANAGE_GUILDS, and OPERATOR access, then verify archived guild and invite behavior with the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100