Fix clicking next/prev arrows when initialSlide is not 0

[jorrit]

This PR fixes #1946.

This bug got introduced with change 1c3d70c. When initialSlide is set, targetSlide was not set to the right value. This is fixed.

Also, I think the intended change of 1c3d70c can be implemented slightly simpler, by just checking if the new value is out of the allowed bounds.

[felipe-gustavo]

Please, merge this

[apntzls]

Hello all, what's the status of this PR, I'm needing this fixed.

[JoaoCSR]

Is there any way we can get a timeline on when to expect this merged?

[yenienRey]

Please, merge this +1

[dramoturg]

Do you have any news?

[gtb104]

This repo has had very little movement in the last year. I see there are many open pull requests just waiting to be merged. Who has write access? If it's only @akiran, can we petition to get others to help maintain this project?

[akiran]

This issue is already fixed

[gtb104]

If it’s already fixed, could you please point to the PR and release that addresses this issue? Ant design uses this library in their Carousel component. If there’s a specific version they should be at, then I’ll make a PR to pull in the correct version on their repo.

[AttackXiaoJinJin]

come on, it's 2022 !!

[nh-teemukorkalainen]

This is still an issue on 2024.

If slider uses beforeChange hook, the next index is always zero and, when set, the current index has the value of the initialSlide-prop. Additionally afterChange hook’s current index is also always zero, even if initialSlide-prop is something else than zero.