v1.1: Add new filter rule _geoBoundingBox

[guimachiavelli]

Closes #2201

[alallema]

I just checked the code-sample but LGTM! 🎉

[maryamsulemani97]

Could you please update the last bullet for the following errors in /reference/errors/error_codes.md:

• invalid_settings_ranking_rules
• invalid_search_sort
• invalid_search_filter

to:

A reserved keyword like _geo, _geoDistance, _geoPoint, _geoRadius or _geoBoundingBox is used…

[guimachiavelli]

@maryamsulemani97: is the list of reserved words exhaustive? If so, does it have to be?

[maryamsulemani97]

is the list of reserved words exhaustive? If so, does it have to be?

It isn't. We can document this somewhere else if needed

[guimachiavelli]

Ok, so after some actual testing I realised there's no "one size fits all" solution here. This is what we'll do:

• invalid_settings_ranking_rules: should include both _geoRadius and _geoBoundingBox. Using any of these words as custom ranking rules (e.g. _geoRadius:asc or _geo:desc) triggers an error
• invalid_search_sort: currently wrong. it says we can't use _geoPoint when not only we can do it, there's no other way of using _geoPoint. should include both _geoRadius and _geoBoundingBox
• invalid_search_filter: correct as it is. should not include _geoBoundingBox nor _geoRadius, as both of these are valid filter rules

[maryamsulemani97]

🍎

[guimachiavelli]

bors merge

[bors]

Build succeeded:

• check-builds (14)
• check-builds (16)
• check-links
• check-style
• vale