Impossible to determine slide direction in `beforeChange` handler with 2 slides

short description of the bug / issue, provide more detail below.

The only parameters we get for the beforeChange handler are event, slick, currentSlide, nextSlide. There is no direction parameter. Therefore, going from currentSlide 0 to nextSlide 1 has ambiguous direction that is impossible to determine without knowing more information. Direction can be calculated if there are more than 2 slides because going left nextSlide would be numSlides -1 which can be used as an exception case in calculating direction.

We simply need a direction parameter to be passed to this handler.

[qikkeronline]

For anyone who needs this behaviour today:

init slick without arrows

    $(".frontpage-slider").slick({
        arrows: false, // disable built in arrows
    });

then implement your own next and prev buttons in your html and implement the following js

    var direction;

    $(document).on('click', '.slick-next', function(){

        direction = 'right';
        $('.frontpage-slider').slick('slickNext');

    });

    $(document).on('click', '.slick-prev', function(){

        direction = 'left';
        $('.frontpage-slider').slick('slickPrev');

    });

And afterwards you can use the direction variable in your beforeChange event 😃

In my case the animations I trigger on the beforeChange event are turned off on mobile devices; hence the above suffices for me. If you need the animations to work on touch devices you’ll need some extra logic.

I still think this would be a great addition to the Slick core; would make an already awesome slider even more awesome 👍

[eballeste]

@notacouch didn’t think about that, maybe by also listening in on the keypress event and checking if it was the enter key should take care of that. oh, also adding the aria button role to it?

regardless, i’ve been saying this in every single issue that I get a new notification from, this project is dead. issues should be reaching 1000 issues now and the only recent pull request was a cosmetic update to show more accurate download numbers in npm.