matrix-org / matrix-org/matrix-spec
Add specific errcodes for application service extension of CS api
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Currently if a application service ghost user doesn't exist, and the AS tries to send an event from that user, Synapse returns:
```
403: {"errcode":"M_FORBIDDEN","error":"Application service has not registered this user"}
```
This is the same status code and errcode as e.g. trying to join a room the ghost user doesn't have permission to join. To understand why the request failed, you have to parse the error message which could be different between HS implementations.
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
No file, test, or entry point is named. Start with the CS API behavior described in the issue and determine where application-service ghost-user errors are specified. Done means defining distinct error codes for this case and documenting behavior that avoids parsing implementation-specific messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100