-
Notifications
You must be signed in to change notification settings - Fork 92
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
Refactorise the errors #234
Conversation
irevoire
commented
Feb 10, 2022
- Merge the two meilisearch error types
- Use Deserialize and Serialize to generate the string associated with every error instead of writing it by hand
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 very good to me. Implementing serde on error highly reduced the amount of code to maintain, that's nice!
@irevoire is it breaking for the users? |
Huum when the user is accessing the error contained in a task he'll get types on the error_code and error_type instead of getting everything as string. |
I rebased on main, you can merge |
bors merge |
I'll release it tomorrow :) |
Build succeeded: |
243: Update version for the next release (v0.15.0) r=brunoocasali a=brunoocasali ##⚠️ Breaking changes * Refactorise the errors, now `error_code` and `error_type` has types instead of `string` (#234) `@irevoire` * Put type on timestamp and duration (#237) `@irevoire` * The `time` crate will be needed if you need to manipulate API keys (check for more info #226, #237 (comment), and meilisearch/integration-guides#121 (comment)). ## 🚀 Enhancements * Refactorise the settings (#235) `@irevoire` Thanks again to `@irevoire!` 🎉 Co-authored-by: Bruno Casali <brunoocasali@gmail.com>