Alex S

> One problem I am facing here. I have indexed the category details in agolia. But I am not able to form the hierarchical menu on the frontend @sandipbhuyan Is...

Thanks for the feedback @gzzo This is not planned as we speak. In the mean time you could be interested in trying to implement your own slider using the [connector](https://community.algolia.com/instantsearch.js/v2/connectors/connectRange.html).

Hi @mwawrusch thanks for reporting this issue. You're right about the return value for the hierarchical facet, it's inconsistent that we return `undefined` when we find no values. Are you...

> We can leverage getHierarchicalFacetBreadcrumb to retrieve the current values for the breadcrumb. Then we can compute the path for each of the value. Should be tested though not sure...

Thanks for summing that up @vvo, I was a bit lost. It makes sense as a solution 👍 . Only thing that might be bothering is where to provide this...

Have you considered having the the instance of the map as a property of the widget and documenting it?

> @bobylito then it would be undefined before mounted right? Probably indeed 😅 . Other idea: what about having a method on the widget instance that returns a promise of...

@samouss I think the support for `Infinity` is linked to the fact that it is provided in the base values (`start`) that as an implementer you want to reuse because...

The tuple vs object problem is mainly good for consistency as we have now two kinds of structure for the same kind of values and it has a slightly better...

@samouss I agree with you that eventually we should get rid of the references to `Infinity`. However in the mean time, this is a value provided by the API (`start`)...