algolia / algolia/instantsearch

Sort refinementList values before sending HTTP request (so request caching works as expected)

Open
#5,258 3 comments 0 reactions 0 assignees View on GitHub
Library: React InstantSearch < 7
Dominant language
TypeScript
Stars
4.1k
Forks
553
Avg merge
1d 11h
Merged PRs (30d)
51

Description

_Deleting my OP to not cause confusion. See my two posts below for the remaining issue, which is refinement list values should probably be sorted before building HTTP request string._

**Environment:**

- OS: Mac
- Browser: Chrome (Reproduced in Firefox & Safari too)
- Version: `"react-instantsearch-dom": "^6.5.0",`

Contributor guide

Open the contributing guide

Research direction

Trace refinementList values from the widget into the HTTP request-building path, then inspect how the request string is assembled and cached. Confirm the behavior with the existing test suite or a focused reproduction if no relevant test is apparent. Done means equivalent value order produces the same request and allows request caching to work as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
api, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.