You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you asking to display custom fields in the interface? Or is the problem that the existence of custom fields appears should be ignored, but instead breaks the minibar component?
I believe it is already supported for the same collection to have additional custom fields. Minibar will only select the standard fields, and the rest should be ignored without error.
What is the expected behaviour you're looking for?
minibar is not specific to the docsearch scraper, but it does need to know what fields to display.
What configuration options do you currently pass to instantsearch?
Could you share an example URL of a typesense request that instantsearch makes when you type?
The UI needs to know what to show. We could easily add an option to override what field to render. A live example would be ideal, to help validate the solution.
If you get an error, please include the details of that error.
Additionally, if you are migrating from a different system, include the name, version, and configuration options you use, and include an example URL of a working TypeSense request made by that other system (e.g. while typing).
It looks like the URL you shared is a request made by minibar.
Activity
Krinkle commentedon Aug 29, 2024
Is this Typesense collection created by typesense-docsearch-scraper?
Are you asking to display custom fields in the interface? Or is the problem that the existence of custom fields appears should be ignored, but instead breaks the minibar component?
I believe it is already supported for the same collection to have additional custom fields. Minibar will only select the standard fields, and the rest should be ignored without error.
What is the expected behaviour you're looking for?
bestony commentedon Aug 30, 2024
not created by https://github.com/typesense/typesense-docsearch-scraper.
I expected typesense-minibar is an alternative for instansearch.js but more lightweight.
maybe typsense-minibar is a tool only for collection created by typesense-docsearch-scraper?
Krinkle commentedon Aug 30, 2024
minibar is not specific to the docsearch scraper, but it does need to know what fields to display.
What configuration options do you currently pass to instantsearch?
Could you share an example URL of a typesense request that instantsearch makes when you type?
The UI needs to know what to show. We could easily add an option to override what field to render. A live example would be ideal, to help validate the solution.
borger-commits commentedon Oct 17, 2026
http://localhost:8108/collections/products/documents/search?per_page=5&query_by=hierarchy.lvl0,hierarchy.lvl1,hierarchy.lvl2,hierarchy.lvl3,hierarchy.lvl4,hierarchy.lvl5,content&include_fields=hierarchy.lvl0,hierarchy.lvl1,hierarchy.lvl2,hierarchy.lvl3,hierarchy.lvl4,hierarchy.lvl5,content,url_without_anchor,url,id&highlight_full_fields=hierarchy.lvl0,hierarchy.lvl1,hierarchy.lvl2,hierarchy.lvl3,hierarchy.lvl4,hierarchy.lvl5,content&group_by=url_without_anchor&group_limit=1&sort_by=item_priority:desc&snippet_threshold=8&highlight_affix_num_tokens=12&x-typesense-api-key=dev-only-change-this-key&q=c
This is the request it makes.
And yes it would be quite useful if there was an option to render only specific fields.
Krinkle commentedon Oct 18, 2026
@borger-commits What problem are you trying to solve?
If you get an error, please include the details of that error.
Additionally, if you are migrating from a different system, include the name, version, and configuration options you use, and include an example URL of a working TypeSense request made by that other system (e.g. while typing).
It looks like the URL you shared is a request made by minibar.