Sebastien Lemieux

I first put a 👍 on @denispodtykan comment, but then removed it. ngx-slick-carousel has it's own load of issues, for us they are a dealbreaker and are pushing us back...

https://github.com/devmark/ngx-slick/issues/39 This is linked to this issue. I manually updated my files in the node_modules directory for a quick test and it worked. I'll submit a PR for this.

See https://github.com/devmark/ngx-slick/pull/58

Hi, We're looking for a fool that won't only does HTML diff, but a CSS diff... We'd like to spot early on changes in CSS done for an issue that...

I'm adding my voice here to this issue. Is there a way to add a link to this issue in the documentation with a note about the current limitation ?...

You don't need ngx-slick to use ngx-slick-carousel. The last part of the documentation explains how to migrate from ngx-slick to ngx-slick-carousel, and the first step is to uninstall the former...

Or have an option to decide if they are open or closed when opening the report, like the showFailed (and others) option.

Digging trough the code, weights seems to go from the highest number to the lowest. Since the file is generated after each test, my understanding is that you need to...

I had a different approach for mochawesome in my project. There's some elements in common with previous solutions : In ```package.json``` ``` "scripts": { "cy:run": "cypress run --browser=chrome", "cy:parallel-test": "cypress-parallel...

https://github.com/PremierTechDigital/cypress-parallel-report For those interested, I built a repository to demonstrate our final solution to run Cypress parallel and get a report. At the end, we have one report, with some...