Update all of typescript-eslint: 5.51.0 → 5.52.0 (minor) #433
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @typescript-eslint/eslint-plugin (5.51.0 → 5.52.0) · Repo · Changelog
Release Notes
5.52.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 15 commits:
chore: publish v5.52.0feat(eslint-plugin): [block-spacing] extending base rule for TS related blocks (#6195)fix(eslint-plugin): [no-unnecessary-condition] fix false positive when checking indexed access types (#6452)feat(eslint-plugin): [explicit-function-return-type] add allowIIFEs option (#6237)chore: check package.json existence in package-packages.ts (#6454)chore(website): use Docusaurus Link component, fix broken link (#6448)fix(eslint-plugin): [no-unnecessary-condition] account for optional chaining on potentially void values (#6432)chore: add merge_group trigger to run ci on the merge queue (#6445)feat(typescript-estree): allow specifying project: true (#6084)fix(eslint-plugin): fix key-spacing when type starts on next line (#6412)feat(eslint-plugin): [explicit-function-return-type] add allowFunctionsWithoutTypeParameters option (#6105)feat(typescript-estree): add `.kind` to `TSModuleDeclaration` (#6443)chore(website): link every rule doc to the playground with default config (#6317)chore: migrated `shared-fixtures` to `ast-spec` (#6436)fix(eslint-plugin): [no-import-type-side-effects] correctly ignore zero-specifier imports (#6444)✳️ @typescript-eslint/parser (5.51.0 → 5.52.0) · Repo · Changelog
Release Notes
5.52.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 15 commits:
chore: publish v5.52.0feat(eslint-plugin): [block-spacing] extending base rule for TS related blocks (#6195)fix(eslint-plugin): [no-unnecessary-condition] fix false positive when checking indexed access types (#6452)feat(eslint-plugin): [explicit-function-return-type] add allowIIFEs option (#6237)chore: check package.json existence in package-packages.ts (#6454)chore(website): use Docusaurus Link component, fix broken link (#6448)fix(eslint-plugin): [no-unnecessary-condition] account for optional chaining on potentially void values (#6432)chore: add merge_group trigger to run ci on the merge queue (#6445)feat(typescript-estree): allow specifying project: true (#6084)fix(eslint-plugin): fix key-spacing when type starts on next line (#6412)feat(eslint-plugin): [explicit-function-return-type] add allowFunctionsWithoutTypeParameters option (#6105)feat(typescript-estree): add `.kind` to `TSModuleDeclaration` (#6443)chore(website): link every rule doc to the playground with default config (#6317)chore: migrated `shared-fixtures` to `ast-spec` (#6436)fix(eslint-plugin): [no-import-type-side-effects] correctly ignore zero-specifier imports (#6444)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands