Zakaria Abu Sarah ザカリヤ
Zakaria Abu Sarah ザカリヤ
Ok, thanks I'll try with an API Key. Still have questions... 1. You state "depends how you're connecting to ElasticSearch" So on what does it depend? 2. Why can't I...
Ah check. Yes I know about not using the browser directly, the connector is connected server-side with nextjs in my case. It works fine with an API-key. Good to know...
What the response state looks like is quite clear already, thank you. I just don't see facets in my response (I got aggregations) from the javascript API, or other fields...
I am coming to the conclusion that it's just not possible to set it up like this. For anybody having the same question: I 'solved' (more of a workaround) this...
Seconded, I would love to add a euro sign instead of a dollar in a lot of icons.
Whoa really old PR but a really important thing since I had no idea how else to differentiate between inline code blocks and others. I am using MDXProvider from @mdx/react...
Thanks for providing a solution as well, same issue with emotion package
> we would would like to allow users to further specify the results they are seeing by allowing them to set a search term on top of the pre-defined filters...
Fully agreed I want t obe able to stack icons easily. I think this was easier in the past before they replaced stacks with layers.
I looked into the package itself: It does look like there is no code related to `filters` at all in the autocomplete folder: `handlers/autocomplete/index.js` while in `handlers/search` there is something...