fix: autoplay interval bug

[ZLevine]

What:

Fixes #252

Automatically pause "autoplay" (isPlaying) when the user changes slides using one of these HOC control components:

• <ButtonNext />
• <ButtonBack />
• <ButtonFirst />
• <ButtonLast />
• <Dot />

This mirrors the existing behavior where autoplay is paused when the user interacts with the Slider (i.e. drags on mobile).

Why:

Currently, the isPlaying interval timer doesn't reset when the user visits a slide using one of these buttons. The end result (as defined in #252) is that a user could progress to a slide and then immediately be progressed to another slide. I don't see why the user would EVER want this to happen.

How:

Set isPlaying: false in the CarouselProvider state in the onClick handler for each of the aforementioned HOCs.

Checklist:

• Documentation added/updated (N/A)
• Typescript definitions updated (N/A)
• Tests added and passing
• Ready to be merged

I meant to create a bugfix/* branch in my repo to merge in but accidentally committed to Master instead; NBD.

[tim-steele]

@ZLevine just so I understand from what I am reading: If a user clicks the back, next, or dot button - the timer isn't reset, it just pauses autoplay?

[ZLevine]

Correct—this mirrors the existing behavior where it pauses autoplay when a user swipes to a new slide on mobile or otherwise interacts with the slider.

I think this makes sense because, if the user is using one of the navigation arrows or clicking individual slides, they probably want to read and control the slider without it progressing on them.

[tim-steele]

@allcontributors please add @ZLevine for code

[allcontributors]

@tim-steele

I've put up a pull request to add @ZLevine! 🎉

[bcarroll22]

🎉 This PR is included in version 1.26.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[Andrew-Jang]

I think this merge resulted a minor bug #314 . Is there a workaround?