matrix-org / matrix-org/mjolnir
Figure out what to do with expected errors in the web api
Open
Nobody has claimed this yet.
A-Appservice
T-Task
- Dominant language
- TypeScript
- Stars
- 445
- Forks
- 75
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 3
Description
E.g. Requesting a mjolnir from a different user https://github.com/matrix-org/mjolnir/tree/mjolnir-appserv/src
Are we going to catch each one explicitly or is there some middleware that lets us render uncaught errors differently
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 by reviewing the web API code under the linked mjolnir-appserv/src path and identify how expected errors are currently surfaced. Decide whether errors such as requesting another user's mjolnir should be handled explicitly or through middleware, then document the desired behavior and verify it with relevant API checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100