Description

The slick package of Ken Wheeler supports lazy loading. So we should also adopt that :)

Description

When creating content on slides (not the first slide) or when changing the settings of a slide.
The guestframe reloads and try to focus the node of the slide.

But when reloading the slide is maybe not selected.
So the focus is on an element in the nirvana.

Steps to Reproduce

1. Create a slide
2. Create a second slide
3. Change for instance the background image on slide 2

Expected behavior

Page reloads and does not scroll right into the nirvana to focus the not selected slide 2.
Maybe focus the parent node instead.

Actual behavior

Page reloads and scrolls to the right where the slide 2 is hidden but the ui tried to focus the element.

[What actually happened]

Affected Versions

Slick: 3.1

Description

The responsive mixins have a typo in their files and node type names:

NodeTypes.Mixin.Repsonsive.Lg.yaml instead of NodeTypes.Mixin.Responsive.Lg.yaml (and so on)

I intended to fix this via a PR, but it is a breaking change, so I don't know if it can be fixed without releasing a major version.

Description

The configuration module shows that we have wrong types for the position.

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency style-loader was updated from 1.1.3 to 1.1.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

style-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Description:
Remove SlickEelHelper and use the Neos Json.stringify for this.

Original issue noerdisch/neos-slick#4

We want to continue the development to we will care for noerdisch/neos-slick#7

Description:
The Fusion prototypes should use Neos.Fusion:Component for better reusability.

Description

After the installation with composer it is not possible to add an slide to the silder element.
Because the "slide element" is not showing up after i have created and slider element on my document tree.
It seem that the slider element is also not an content collection.

Steps to Reproduce

1. install it with composer and neos 5.0
2. open some page and add a slider element
3. try to add an slide element

Expected behavior

After i have added an slider it should be possible to add an slide element.

Actual behavior

[What actually happened]

Affected Versions

Neos: 5.2.2

Slick: v3.3.2

You can get this information by running composer show or using the package management module within Neos.

When you use windows based browsers the content slider renders a scrollbar

Description

Changed the branch for release trigger from master to release but for some reason the release of 3.2.0 was triggered on master.

After TravisCI has been acquired and the company fired a lot of the awesome developers we should switch to CircleCI. Don´t want to support such behavior.

The library is pretty old and comes with jquery as dependency. Would be better to use vanilla js or a pretty small library like preact ⚛️

Description

We still use webpack 4 and some dependencies are outdated as the amout of dependabot PRs shows.
So we should upgrade the whole toolchain.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

As it is a neos package and neos is under GPL-3 so se need to use the license as well.