Closed getorca closed 5 years ago
Hey @getorca, which version of ReactiveSearch is this issue happening with?
@siddharthlatest reactivesearch 2.18.0 reactivemaps 2.0.1
It could also be related to a reactivemaps component, the custom query is on a GeoDistanceDropdown search filter.
Thanks! We've fixed this behavior in v3, currently on 3.0.0-rc.0
release.
Thanks! We've fixed this behavior in v3, currently on
3.0.0-rc.0
release.
@siddharthlatest I'm experiencing the same behaviour in 3.0.0-rc.3 as mentioned above
I don't think we support this behavior in reactive-maps.
okay, might not be a bug, but an unexpected behaviour. Should probably update the docs and examples that mention "in the format of Elasticsearch Query DSL"
<GeoDistanceDropdown
...
className="custom-class"
style={{"paddingBottom": "10px"}}
customQuery={
function(location, distance, props) {
return {
// query in the format of Elasticsearch Query DSL
geo_distance: {
distance: distance + props.unit,
location_dataField: location
}
}
}
}
https://opensource.appbase.io/reactive-manual/v3/map-components/geodistancedropdown.html
Issue Type: bug
Platform: ReactiveSearch for Web 2.18.0 ReactiveMaps 2.0.1
Description: Including script_fields in the customquery on a GeoDistanceDropdown the query DSL doesn't contain the script_fields. ie. script_fields is dropped form the DSL.
The request body for the query has dropped the script_fields