update transformRangeFilterValue to use gte and lte over from and to #1160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before submitting this PR:
to this repository.
applicable).
react-search-ui-views
storybook (if applicable).
Description
previously when this package leveraged searchkit set gte: and lte: inside the request body for range queries.
https://github.com/searchkit/searchkit/blob/3805f655363e8a72a534807026aee67d01536d3a/packages/searchkit-sdk/src/facets/MultiQueryOptionsFacet.ts#L20
Apparently there is an issue with the type declarations in @elastic/elasticsearch where it says from: and to: are valid properties of a range query (they aren't)
https://github.com/elastic/elasticsearch-js/blob/0a14ecca4e10f18ec25e358a38bdb23c44b0d374/src/api/types.ts#L9391
List of changes
This PR updates the transformRangeFilterValue to set gte and lte as required by the elasticsearch DSL.
Associated Github Issues
elastic/elasticsearch-js#2846