-
Notifications
You must be signed in to change notification settings - Fork 391
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7afbed9:
|
✔️ Deploy Preview for react-instantsearch ready! 🔨 Explore the source changes: 7afbed9 🔍 Inspect the deploy log: https://app.netlify.com/sites/react-instantsearch/deploys/619d41b552e6c900072dab6a 😎 Browse the preview: https://deploy-preview-3198--react-instantsearch.netlify.app |
963a75d
to
f8660a2
Compare
refine([from, to]); | ||
}} | ||
> | ||
<input |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use the step
property?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can set it, I'm not really a fan on how precision gets turned into step in InstantSearch.js, seems like needless indirection
Summary
implement useRange
Result
example implemented RangeInput with approximately the same code as existing React InstantSearch, with the value/start transformations done in InstantSearch as well: https://github.com/algolia/instantsearch.js/blob/dcbbd8804b4b6471d24820b42826b57388974c27/src/widgets/range-input/range-input.tsx#L144-L154
FX-443