Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 3752 by Publicize a list of taken WebAPIError error code blocks from public extensions

*** For customer support, please post to
*** If you have a patch, please submit it to
*** Do not post confidential information in this enhancement request!

What version are you running?

What's the URL of the page this enhancement relates to, if any?

Describe the enhancement and the motivation for it.

We're developing some extensions with WebAPIResource's, and we're developing new WebAPIError's for these endpoints. We're not sure what we're supposed to be choosing for the WebAPIError error codes (not the HTTP status codes). They seem to be arbitrarily chosen. At this point, we just know we should probably avoid colliding with any error codes from Review Board, Djblets or any of our other extensions.

I can see this becoming more of an issue as more and more extensions become available and introduce new WebAPIErrors. I'm really not sure how best (or how necessary it is) to avoid collisions with other WebAPIError status codes. One thing I was thinking about was having some code in the package store that scans Review Board extensions for WebAPIErrors and collects the codes that are being used, and provide a list of those error codes. That way, a developer could choose wisely and avoid collision.

What operating system are you using? What browser?

Please provide any additional information below.

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to