feat: Remove deprecated formatting rules #103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions bot
pushed a commit
that referenced
this pull request
Nov 6, 2023
# [37.0.0-beta.1](v36.0.0...v37.0.0-beta.1) (2023-11-06) ### Features * Remove deprecated formatting rules ([#103](#103)) ([deab90a](deab90a)) ### BREAKING CHANGES * All formatting rules have been removed as they have been deprecated by ESLint (see eslint.org/blog/2023/10/deprecating-formatting-rules). We won't switch to @stylistic/eslint-plugin-js as code formatting should be done by Prettier nowadays.
|
🎉 This PR is included in version 37.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
github-actions bot
pushed a commit
that referenced
this pull request
Nov 6, 2023
# [37.0.0](v36.0.0...v37.0.0) (2023-11-06) ### Features * Add new base rules ([#105](#105)) ([10d01ed](10d01ed)) * New beta release ([c358189](c358189)) * Remove deprecated formatting rules ([#103](#103)) ([deab90a](deab90a)) * Remove special handling for Prettier ([#104](#104)) ([068b731](068b731)) ### BREAKING CHANGES * Some new base rules have been introduced which might produce linting errors. * The `prettier-` prefix has been removed from all preset files: `peerigon/presets/prettier-typescript.js` becomes `peerigon/presets/typescript.js`, `peerigon/presets/prettier-typescript-react.js` becomes `peerigon/presets/typescript-react.js` and `peerigon/presets/prettier-typescript-node.js` becomes `peerigon/presets/typescript-node.js` * All formatting rules have been removed as they have been deprecated by ESLint (see eslint.org/blog/2023/10/deprecating-formatting-rules). We won't switch to @stylistic/eslint-plugin-js as code formatting should be done by Prettier nowadays.
|
🎉 This PR is included in version 37.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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: All formatting rules have been removed as they have been deprecated by ESLint (see https://eslint.org/blog/2023/10/deprecating-formatting-rules/). We won't switch to @stylistic/eslint-plugin-js as code formatting should be done by Prettier nowadays.