Closed itaiperi closed 6 months ago
Name | Link |
---|---|
Latest commit | c3079257f12164e24d6f213afb90873004bcfc88 |
Latest deploy log | https://app.netlify.com/sites/react-daisyui/deploys/65906fadf9ee9c0008c126d1 |
Name | Link |
---|---|
Latest commit | f9fe9a55fb1c02a71a8043eae06b6e2f4e8ad44a |
Latest deploy log | https://app.netlify.com/sites/react-daisyui/deploys/65907d819041bd000894a877 |
Deploy Preview | https://deploy-preview-438--react-daisyui.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | c3079257f12164e24d6f213afb90873004bcfc88 |
Latest deploy log | https://app.netlify.com/sites/react-daisyui/deploys/65906fadf9ee9c0008c126d1 |
Also, removed usage of useMemo
, as there's no actual use for it, and the computation is fairly simple
This PR fixes #437.
In a nutshell:
Range
component ticks math is wrong, only takes into account range [0, 100] and no step sizes < 1. Also, ticks are always displayed whenstep
is provided, whether you want to or not.displayTicks
andticksStep
parameters to control when to display ticks, and what the ticks step size should be, which can now be different thanstep
(before, they were the same by design). Also, take into accountprops.min
andprops.max
to allow for the range the user intended in the ticks.