-
Notifications
You must be signed in to change notification settings - Fork 90
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
Remove jsonindex #278
Remove jsonindex #278
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.
Hey, the PR looks really good!
Thanks a lot for your contribution 🎉
1d12c29
to
c7d2715
Compare
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.
@bidoubiwa or @brunoocasali, this PR looks good to me, I think we can merge when one of you have the time to review it 😁
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.
Hi @abhizer thanks a lot for your contribution, it is really appreciated ❤️
I left some comments in your PR, just to make sure I understood everything!
Commit Suggestion: Avoid creating a new Index in get_raw_index Co-authored-by: Bruno Casali <brunoocasali@gmail.com>
Commit Suggestion: Make test_fetch_info more readable Co-authored-by: Bruno Casali <brunoocasali@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.
Thanks for your contribution @abhizer ❤️
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 your contribution once again!
yes that's super breaking |
Should the code-samples be updated here? |
Went through the code samples, didn't notice anything that'd need to be changed. |
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
278: Remove jsonindex r=bidoubiwa a=abhizer # Pull Request ## What does this PR do? Fixes #187 #187 ## PR checklist Please check if your PR fulfills the following requirements: - [x] Does this PR fix an existing issue? - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes? ## Todo List: - [x] Add fields updated_at, created_at and primary_key to Index - [x] Make get_raw_index return the raw Value that's returned by Meilisearch - [x] Update fetch_info to update Index instead of returning JsonIndex - [x] Remove JsonIndex and update everything (like get_raw_index) that relies on it to use Index - [x] Tests *P.S.: I think this requires a thorough review, as a lot of things have been changed.* Thank you so much for contributing to Meilisearch! Co-authored-by: Abhinav Gyawali <22275402+abhizer@users.noreply.github.com>
Build failed: |
bors try |
tryBuild succeeded: |
bors merge |
Build succeeded: |
287: Update version for the next release (v0.17.0) r=curquiza a=brunoocasali This version makes this package compatible with Meilisearch v0.27.0 🎉 Check out the changelog of [Meilisearch v0.27.0](https://github.com/meilisearch/meilisearch/releases/tag/v0.27.0) for more information on the changes. ##⚠️ Breaking changes * Remove jsonindex (#278) `@abhizer` ## 🚀 Enhancements * Add cli-app example to meilisearch-rust (#279) `@salugi` * Ensure nested field support (#273) `@bidoubiwa` * Add new search parameters `highlightPreTag`, `highlightPostTag` and `cropMarker` (#274) `@bidoubiwa` * Add User-Agent header to have analytics in every HTTP request (#254) `@brunoocasali` Analytics is enabled by default in the server, but you can disable them by following [this guide](https://docs.meilisearch.com/learn/what_is_meilisearch/telemetry.html#how-to-disable-data-collection) Also, of course, every analytics data we collect are **ANONYMOUS** [read the guide for more information](https://docs.meilisearch.com/learn/what_is_meilisearch/telemetry.html). Thanks again to `@abhizer,` `@bidoubiwa,` `@irevoire,` `@salugi` and a1! 🎉 Co-authored-by: Bruno Casali <brunoocasali@gmail.com>
Pull Request
What does this PR do?
Fixes #187
#187
PR checklist
Please check if your PR fulfills the following requirements:
Todo List:
P.S.: I think this requires a thorough review, as a lot of things have been changed.
Thank you so much for contributing to Meilisearch!