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

Explicitly specify all rule options #1003

Closed
rostislav-simonik opened this issue Dec 14, 2022 · 2 comments · Fixed by #1503
Closed

Explicitly specify all rule options #1003

rostislav-simonik opened this issue Dec 14, 2022 · 2 comments · Fixed by #1503
Labels

Comments

@rostislav-simonik
Copy link
Collaborator

To prevent unintentional changes on plugin bumps.

@mightyiam
Copy link
Owner

Upstream doesn't yet have this policy. Proof. Rule has options. So we're not adopting this policy yet.

standard/eslint-config-standard#375

mightyiam added a commit that referenced this issue Apr 7, 2024
closes #1003

BREAKING CHANGE: (trying to) specify all options for rules that are used.
Most likely will not affect you.
eslint-config-love-release-bot bot pushed a commit that referenced this issue Apr 7, 2024
## [46.0.0](v45.0.0...v46.0.0) (2024-04-07)

### ⚠ BREAKING CHANGES

* (trying to) specify all options for rules that are used.
Most likely will not affect you.

### Features

* try to specify all options for used rules ([dc6ad6a](dc6ad6a)), closes [#1003](#1003)

### Testing

* exported value deep equality ([c869c59](c869c59))
@eslint-config-love-release-bot

🎉 This issue has been resolved in version 46.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

2 participants