Skip to content

Conversation

@yannickcr
Copy link
Contributor

Description

Backport of #3671 for InstantSearch v2.

Original description:

An issue raised by a customer is that when selecting more than 20 values with the routing option activated, the data structure returned by the parseURL function changes.

qs by default converts arrays with more than 20 items to an object. We want to avoid this because the data structure manipulated can therefore vary.

Setting the limit to 100 seems a good number because the engine's default is 100. It can go up to 1000 but it is very unlikely to select more than 100 items in the UI.

Reference

@algobot
Copy link
Contributor

algobot commented Jul 10, 2019

Deploy preview for instantsearchjs ready!

Built with commit 6079fd4

https://deploy-preview-3935--instantsearchjs.netlify.com

Copy link
Contributor

@Haroenv Haroenv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really back port features on v2?

@francoischalifour
Copy link
Contributor

@Haroenv Since this is an easy fix and that this one was implemented already, I guess it's fine?

@yannickcr yannickcr merged commit d6476e2 into v2 Jul 10, 2019
@yannickcr yannickcr deleted the fix/routing-parsing-urls-100-v2 branch July 10, 2019 13:01
yannickcr added a commit that referenced this pull request Jul 10, 2019
<a name="2.10.5"></a>

* **routing:** enforce RoutingManager is the last widget ([#3149](#3149)) ([1e86b2e](1e86b2e)), closes [#3148](#3148)
* **routing:** support parsing URLs with up to 100 refinements ([#3935](#3935)) ([d6476e2](d6476e2))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants