We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
_geo
Starting with v0.28, _geo fields (both lat and lng) should accept numbers in both numeric and string formats:
lat
lng
"_geo": { "lat": 0.0, // floating point number, valid "lng": "0.0" // a string that can be adequately converted into a float, also valid }
We need to update the Geosearch guide so this is stated clearly.
Spec: meilisearch/specifications#83 Issue on core: meilisearch/meilisearch#2354 SME: @irevoire
The text was updated successfully, but these errors were encountered:
Merge #1735
13459d7
1735: v0.28: accepted `_geo` `lat`, `lng` types r=maryamsulemani97 a=guimachiavelli Closes #1694 Co-authored-by: gui machiavelli <[email protected]>
Merge #1707
00cb6df
1707: v0.28 r=guimachiavelli a=guimachiavelli This is a staging PR for all changes related to Meilisearch v0.28. Please avoid making changes directly to this PR; instead, create new child branches based off this one. Closes #1687, #1688, #1691, #1692, #1693, #1694, #1699, #1700, #1701, #1702, #1703, #1704, #1706, #1722, #1727, #561 Co-authored-by: gui machiavelli <[email protected]> Co-authored-by: gui machiavelli <[email protected]> Co-authored-by: Tommy Melvin <[email protected]> Co-authored-by: Maryam Sulemani <[email protected]> Co-authored-by: Maryam <[email protected]>
guimachiavelli
Successfully merging a pull request may close this issue.
Starting with v0.28,
_geo
fields (bothlat
andlng
) should accept numbers in both numeric and string formats:We need to update the Geosearch guide so this is stated clearly.
References
Spec: meilisearch/specifications#83
Issue on core: meilisearch/meilisearch#2354
SME: @irevoire
The text was updated successfully, but these errors were encountered: