-
Notifications
You must be signed in to change notification settings - Fork 115
Add error codes #139
Add error codes #139
Conversation
Fix: OR queries require an array of values
…eads Updated migration docs
Co-authored-by: Matej Bačo <matejbaco2000@gmail.com>
Fix upgrade docs and added stop + uninstall
Fix broken specs docs
Specs bug fix
Fixed indexes case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What should we do with the 1st table in the page? I feel the difference between them is not very clear for the reader.
@eldadfux the first table talks about the convention we follow when deciding an HTTP status code for our errors. And the second table talks more about Appwrite specific error codes. |
I would only consider adding the version we started supporting each error code. We have something similar for env vars. |
@eldadfux In this case, I'm not sure we can follow the convention we use for ENV Vars. Since we introduced all these error codes in 0.13. literally every row in the table will have this information and it'll just make the table very noisy. It's probably a better option to mention that this feature was introduced in From 0.14 onwards, we can start following the ENV Vars convention |
@eldadfux updated the description to add the note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM <3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changed target branch to 0.13 |
Uh oh!
There was an error while loading. Please reload this page.