Just a heads up that I've moved your question to the Elastic Search label since you're asking about search-ui.
I see in the issue that you reference that it's marked with a wont fix label as it's stale. Have you commented on the issue with the details to request an update? You might get some more detail there. If not if you can give some detail on what you're trying to do with this in your custom connector I can try and follow up.
The main issue we're facing is with the combination of from next/link and triggering the search.
Navigating to the search results with does not trigger a new call to the endpoint as it does with the rest of the non elastic endpoints we are using.
Based on some of these pass discussions and the wont fix issue on github it seems like maybe people have experienced something similar to this? Although I haven't found any answers that are helpful for Next 14 with the app directory.
I would be happy to provide more detail if needed. Thank you very much!
Thanks @kudumine, another user who had a similar issue got some inspiration from this post on Next 13. I think they applied this method for 14 and it worked well. They were also doing some custom routing as well.
I found these two community resources (but I'm a bit unclear on the versions) as well that may be helpful:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.