-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[No QA] Add documentation about error onyx best practice under API.md #9629
Conversation
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.
Nice, simple and to the point. I agree with Aldo's suggestion.
Co-authored-by: Aldo Canepa Garay <87341702+aldo-expensify@users.noreply.github.com>
Co-authored-by: Robert Chen <robert@expensify.com>
cc49970
Co-authored-by: Maria D'Costa <maria@expensify.com>
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.
Thanks for adding, looks good
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @yuwenmemon in version: 1.1.81-0 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.1.82-5 🚀
|
Pullerbearing (@neil-marcellini)
cc @nkuoch @marcaaron @tgolen @iwiznia @Julesssss @MariaHCD @aldo-expensify @luacmartins
Details
Adding what was discussed in this thread about errors returned and stored in Onyx being stored under
error
Fixed Issues
None
Tests
None