snowykami/meilisearch
1
0
Fork 0
mirror of https://github.com/meilisearch/meilisearch.git synced 2025-09-06 04:36:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve error message

Browse Source
This commit is contained in:
Mubelotix
2025-08-19 14:29:07 +02:00
parent bfb6cdc16b
commit 2ddecc311f
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
crates/filter-parser/src/error.rs
View File

@ -213,7 +213,7 @@ impl Display for Error<'_> {
writeln!(f, "The `_geoPolygon` filter expects at least 2 points")?; writeln!(f, "The `_geoPolygon` filter expects at least 2 points")?;
} }
ErrorKind::GeoCoordinatesNotPair(number) => { ErrorKind::GeoCoordinatesNotPair(number) => {
writeln!(f, "Expected coordinates in the form of a pair of numbers but found a group of {number} numbers instead.")? writeln!(f, "Was expecting 2 coordinates but instead found {number}.")?
} }
ErrorKind::ReservedGeo(name) => { ErrorKind::ReservedGeo(name) => {
writeln!(f, "`{}` is a reserved keyword and thus can't be used as a filter expression. Use the `_geoRadius(latitude, longitude, distance)` or `_geoBoundingBox([latitude, longitude], [latitude, longitude])` built-in rules to filter on `_geo` coordinates.", name.escape_debug())? writeln!(f, "`{}` is a reserved keyword and thus can't be used as a filter expression. Use the `_geoRadius(latitude, longitude, distance)` or `_geoBoundingBox([latitude, longitude], [latitude, longitude])` built-in rules to filter on `_geo` coordinates.", name.escape_debug())?

2
crates/filter-parser/src/lib.rs
View File

@ -950,7 +950,7 @@ pub mod tests {
"); ");
insta::assert_snapshot!(p("_geoPolygon([1,2],[1,2,3])"), @r" insta::assert_snapshot!(p("_geoPolygon([1,2],[1,2,3])"), @r"
Expected coordinates in the form of a pair of numbers but found a group of 3 numbers instead. Was expecting 2 coordinates but instead found 3.
20:21 _geoPolygon([1,2],[1,2,3]) 20:21 _geoPolygon([1,2],[1,2,3])
"); ");