-
Notifications
You must be signed in to change notification settings - Fork 28
fix(go): handle HTML errors [skip-bc] #4096
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
Conversation
✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
4a67c4d to
be36096
Compare
shortcuts
left a comment
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.
looks much cleaner! let's not forget to add a test when we do other clients
shortcuts
left a comment
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.
meant to approve gg
Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
algolia/api-clients-automation#4096 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
🧭 What and Why
GCP Cloud Armor can return raw HTML error, we can catch them and handle them gracefully instead of failing the json deserialization.