Joe McElroy

sounds like a bug within Searchkit for highlighting on object fields. This is the code for [highlighting](https://github.com/searchkit/searchkit/blob/main/packages/searchkit/src/highlightUtils.ts#L24) and [tests](https://github.com/searchkit/searchkit/blob/main/packages/searchkit/src/___tests___/highlightUtils.test.ts). Likely will take me next weekend to look into this but...

found the issue that instantsearch requires object fields to be represented in a object hierarchy, not currently as a 1 depth dot notation keys. Fixed this by transforming ES dot...

thanks, will put this under buglist. Happy to accept a PR for this too :)

thanks for the contribution! Suggestion: rather than having two functions, have one function that a developer can optionally pass in that transforms the elasticsearch document and returns a langchain document?...

This looks great BTW and sorry missed this. Thank you for your contribution!

we are still discussing the plans for Search UI. The plan currently is for us to: - GA elasticsearch-connector and introduce a major version of Search UI (2.0) - deprecate...

this has been implemented. See documentation https://docs.elastic.co/search-ui/api/core/configuration#routing-options

Hi there, No news, and not planned. Alternatives are using www.github.com/searchkit/searchkit which does support nested fields for facets and field results.

there is a feature in Search UI which allows you to control the URL serialisation / deserialisation. See `routingOptions` documentation https://docs.elastic.co/search-ui/api/core/configuration#routing-options

im closing this ticket until the API supports such feature.