Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a full reference of all the different error codes (SPEC-309) #140

Open
matrixbot opened this issue Dec 21, 2015 · 0 comments
Open
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@matrixbot
Copy link
Member

Section 2 of the client-server API spec (API Standards) ends with a list of "some standard error codes" but it'd be great to have a reference for the full list of error codes and their meanings. I think right now they're just mentioned in the descriptions for the various API endpoints that might generate them, but this makes it harder to discover them. A gold star change for this issue would be to have a comprehensive list that also includes which endpoints might produce each error, perhaps linked to the relevant section of the spec.

(Imported from https://matrix.org/jira/browse/SPEC-309)

(Reported by Jimmy Cuadra)

@matrixbot matrixbot changed the title Provide a full reference of all the different error codes Provide a full reference of all the different error codes (SPEC-309) Oct 31, 2016
@matrixbot matrixbot added the enhancement A suggestion for a relatively simple improvement to the protocol label Nov 7, 2016
@turt2live turt2live assigned turt2live and unassigned turt2live Aug 31, 2018
@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Sep 5, 2018
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Development

No branches or pull requests

2 participants