apisearch-io / search-ui Goto Github PK

Allow users to pin items in another set of results.

• Add a load more button
• Force the automatic infinite scroll to work only with the wheel
• Add a loading code

A widget to manage the current page using the javascript client.

MultipleFilter widget preloads all aggregations every time and this makes every query super heavy and increases the response time. Even if the limit of items is set and "Show more" button is on, all data is loaded. So when we click to "Show more", the data is already loaded, we only hide or show the items. And this is bad. Because if we have 1000 aggregations to load, this will be queried each time.

Solution: when limiting the items (aggregations) shown on the widget, only query this items. Not all of them. And when clicking show more, the rest of items will be queried.

const multipleFilterWidget = ui.widgets.multipleFilter({
    target: "#authors-filter",
    name: "author",
    filterField: "author_id",
    limit: 5,  // <-- this limit
    showMoreActive: true
})

Add a parameter on template property to write some label for the SortBy Component.

It should be good to have an option on widget configuration to decide whether to trigger the search when user is typing or when pressing enter.

Widget file: https://github.com/puntmig/javascript-search-ui/blob/master/src/Widgets/SimpleSearch/SimpleSearchComponent.js

In order to reduce some first-results loads, we can work with certain events before making the first load

• When the UI result widget is visible in the browser (we could check if it's possible to define this value a number of pixels before to increase UI and reduce this effect as much as possible)
• When the user clicks in the search engine

given an object, where the key is the translation key, and the value the translation, we should add the possibility to work with translatable texts in all the templates.

To keep SEO friendly we should use HTML5 history.

https://css-tricks.com/using-the-html5-history-api/
https://developer.mozilla.org/en-US/docs/Web/API/History_API

WDYT?

Seems that the slider does not return to original position.

When using MultipleFilter widget to refine a search based on a "rating" values, with our logic-less template engine there is no way to transform the given rating number to a star icons. This is just an example, but there are a lot more.

It would be useful to have an attribute, something like dataHelper or dataTransformer to transform the received data before is being passed to the template compiler.

Instead of changing on range input changes, add a manual trigger button as an option

Possibility to add a parameter, something like promotedItems on ResultComponent to promote some items on the result search.

Also to add a parameter like excludedItems on ResultComponent to exclude some items on the result search.

We can anticipate the results when we think that the use will require it.

• On paginate item focus (both pagination and infinite scroll load more button - #39)

We could add a human-language representation as well, like Get 10 items like "my text" with categories X, Y, Z and brands J, Q, K, sorted by name ascending

Hi!
Two fast questions:

1. How to create range filter?
2. How to add own condition to search, which can no visible in filters, e.g. I have static page with category ?category_id =300, and I want saw only items only from this category without button check filter.