1.9 introduces a breaking change
See original GitHub issue1.9 just got pulled into my libraries, as I only contrain by minor version, but it looks like the slides are now wrapped with an extra div
, so my handlers stopped working. Perhaps you should have released as 2.0?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
Chapter 30. Migration Guide
Versions 2.30+ do not introduce nothing breaking, however version 2.29.1 has a major change which means migration of Jersey to Jakarta EE (8)...
Read more >Portal 9.2.10.x release - Potential Breaking Change
Change Introduced. As part of 9.2.10.x release, default Jquery library used by Portal is upgraded from 1.12.4 version to 3.0.0.0 version to improve...
Read more >Implementation of Breaking changes in .com deployments
Currently devopsenablement is on track with breaking changes that require %13.0. ... If the user's cluster is Kubernetes 1.9 or below, this breaking...
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It...
Read more >Kubernetes API and Feature Removals In 1.22
22 and explains how each of those APIs change between beta and stable. What to do. We're going to run through each of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@hypeJunction - Add
rows: 0
to your init to get rid of the extra<div>
.Semver does not allow breaking changes in minor releases. Unless the project specifically defines what is covered by the backwards compatibility policy and excludes DOM structure from BC breaks, which I think would be a mistake in case of a plugin that relies on specific DOM structure to function.