refactor(linter)!: remove tree_shaking plugin#7372
Merged
graphite-app[bot] merged 1 commit intomainfrom Nov 20, 2024
Merged
Conversation
Contributor
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
github-actions
bot
added
A-linter
Contributor
Merge activity
|
Boshen
force-pushed
the
11-20-refactor_linter_remove_tree_shaking_plugin
branch
from
f189741 to
7bf970a
Compare
graphite-app
bot
deleted the
11-20-refactor_linter_remove_tree_shaking_plugin
branch
CodSpeed Performance ReportMerging #7372 will not alter performanceComparing Summary
|
Boshen
added a commit
that referenced
this pull request
Nov 21, 2024
## [0.13.0] - 2024-11-21 - 7bf970a linter: [**BREAKING**] Remove tree_shaking plugin (#7372) (Boshen) - 7f8747d linter: Implement `react/no-array-index-key` (#6960) (BitterGourd) ### Features - be152c0 linter: Add `typescript/no-require-imports` rule (#7315) (Dmitry Zakharov) - 849489e linter: Add suggestion for no-console (#4312) (DonIsaac) - 8cebdc8 linter: Allow appending plugins in override (#7379) (camchenry) - 8cfea3c oxc_cfg: Add implicit return instruction (#5568) (IWANABETHATGUY) - e6922df parser: Fix incorrect AST for `x?.f<T>()` (#7387) (Boshen) ### Bug Fixes - e91c287 linter: Fix panic in react/no-array-index-key (#7395) (Boshen) - a32f5a7 linter/no-array-index-key: Compile error due to it uses a renamed API (#7391) (Dunqing) - 666b6c1 parser: Add missing `ChainExpression` in optional `TSInstantiationExpression` (#7371) (Boshen) ### Documentation - df143ca linter: Add docs for config settings (#4827) (DonIsaac) - ad44cfa linter: Import/first options (#7381) (Zak) ### Refactor - c34d649 linter: Use `scope_id` etc methods (#7394) (overlookmotel) - 466f395 vscode: Split `ConfigService` and `Config` (#7376) (Alexander S.) Co-authored-by: Boshen <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This rule has been in
nurseryfor a long time and I don't see itcoming out of
nurseryin the foreseeable future.closes #7031
clsoes #7057