@akiran Seems like this commit #624 was removed from version 0.14.8 and needs to be remerged.
@akiran Updated to 0.14.11. Seems like #624 has not been remerged and still experiencing this error.
i am experiencing the same issue for 0.14.11.
I am experiencing this error on 0.14.11 as well.
@akiran I am experiencing this error as well, please remerge.
It's not an error. It's just a warning. I'm sending a PR to fix this, hope it's accepted ASAP.
I just hit this.
For anyone else slightly confused:
If you implement your own prev/next arrows react-slick will pass currentSlide and slideCount props to your custom components. It's on you not to place these properties on tags that shouldn't have them. The following is how I dealt with this.
export const CustomArrow = props => {
// pull off props that don't belong on a <button> tag
const { currentSlide, slideCount, ...remainingProps } = props
return (
<button {...remainingProps}>
My Btn
</button>
)
}
You have to follow solution mentioned by @kjs3
Most helpful comment
I just hit this.
For anyone else slightly confused:
If you implement your own prev/next arrows react-slick will pass
currentSlideandslideCountprops to your custom components. It's on you not to place these properties on tags that shouldn't have them. The following is how I dealt with this.