-
Notifications
You must be signed in to change notification settings - Fork 91
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 settings #235
Conversation
get rid of the IntoVecString trait Apply review comments Co-authored-by: Clément Renault <renault.cle@gmail.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.
Looks good to me! Thank you, Tamo!
Is it breaking for the user or is it only internal refactoring? |
It's only internal and should be more flexible for the user. |
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.
💪
bors merge |
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>
This PR unifies the two types
Settings
.It also gets rids of the
IntoVecString
in favor of a simplerIntoIterator<Item = AsRef<str>>
, which is more versatile and common in rust.