Accept null
as a valid geo field
#586
Replies: 4 comments 2 replies
-
I agree, I don't consider this change as breaking personally
|
Beta Was this translation helpful? Give feedback.
-
I agree with both of you, we should make that change. Can we schedule it for Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hello, everyone following this discussion 👋 We have just released the first RC (release candidate) of Meilisearch containing this new implementation! You can test it by using docker run -it --rm -p 7700:7700 -v $(pwd)/meili_data:/meili_data getmeili/meilisearch:v1.1.0-rc.0 You are welcome to communicate any feedback about this new implementation in this discussion. If you encounter any bugs, please report them here. 🎉 Official and stable release containing this change will be available on 3rd April 2023 |
Beta Was this translation helpful? Give feedback.
-
Hey folks 👋 v1.1 has been released. Meilisearch now support the |
Beta Was this translation helpful? Give feedback.
-
I just realized that in a lot of strongly typed language, you're going to send all the fields of your object.
Thus, if some of your documents have a geo field and others don't (which is really common), there is good luck you're going to send a
"_geo": null,
in your document.Maybe we should accept that value as a non-set geo field instead of throwing an error?
Also, it's non-breaking, thus it can be done after the v1.0.
Beta Was this translation helpful? Give feedback.
All reactions