Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commit f272517 is a breaking change to 0.33.0 (Update MD024/no-duplicate-heading to remove duplicate parameter allow…) #1121

Closed
svew opened this issue Feb 5, 2024 · 2 comments
Labels

Comments

@svew
Copy link

svew commented Feb 5, 2024

This change removed allow_different_nesting as an allowed parameter of MD024.

This is a logic change that not only deprecates allow_different_nesting, but also changes the underlying logic. This has recently caused issues for our team as we had our configuration set to:

MD024:
  siblings_only: false
  allow_different_nesting: true

This logic change breaks backwards compatibility, and as such should institute a semver major version change.

The behaviour should be patched on existing 0.x.x releases, and either be reverted on main or induce a major version change.

@DavidAnson
Copy link
Owner

I'm sorry for the inconvenience, but the change you link to does not represent a change of behavior for the rule, merely the removal of one of two redundant names for a parameter. The remaining parameter name behaves the same as it did before the change. Your scenario should work the same as before once you set siblings_only to true.

For what it's worth, semantic versioning rule 7 (that you link to) does not apply here. Rule number 4 is the relevant one and allows changes such as this one.

@svew
Copy link
Author

svew commented Feb 5, 2024

I definitely do not agree that this doesn't represent a breaking change in behaviour. If in 0.32.0, I have a perfectly valid configuration file and everything works fine, but upon upgrading to 0.33.0, suddenly markdownlint starts erroring on docs that it previously didn't, how could that be anything other than a change in behaviour?

However, as you mentioned (and as I forgot 🤦), 0.x.x is an experimental version and doesn't guarentee stable API, so I'll close this ticket and freeze our version of markdownlint that we use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants