Wrong typings for facet search(Cluster.searchQuery)
Description
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Attachments
2
- 12 Mar 2021, 07:30 PM
- 25 Dec 2020, 08:52 PM
Activity
Show:
Jeremy Groh March 12, 2021 at 7:30 PM
I'd like to provide a bit of clarity on this issue. It's not that the `SearchFacet` definition is wrong, rather, I believe it's the type definitions of the functions within `SearchFacet` that are not correct. I've been able to update a local instance using the following definitions, which work great.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Brett Lawson
Brett LawsonReporter
Roman Maidanskyi
Roman MaidanskyiStory Points
1
Components
Fix versions
Affects versions
Priority
MajorInstabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Sentry
Linked Issues
Sentry
Linked Issues
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Created December 25, 2020 at 8:57 PM
Updated May 6, 2021 at 9:10 PM
Resolved May 6, 2021 at 9:10 PM
Instabug
Here is definition of `searchQuery` method
As you see id accept facets and sort. it is wrong typings because facets accept something like this:
```
facets: {
"countryFacet": {
field: "country",
size: 10
},
"cityFacet": {
field: "city",
size: 10
},
....
}
```
Also, the `sort` field accepts an array of objects, but as we see according to typings it is just one object