forked from Pissandshittium/pissandshittium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WebUI: Update @typescript-eslint/{eslint-plugin,parser} to v6.7.4.
This is a necessary preparatory step for updating TypeScript to v5.2 in a follow-up CL. The new version has moved the location of the main binary, from node_modules/@typescript-eslint/parser to node_modules/@typescript-eslint/parser/dist/index.js. Updated to the new path in several .eslintrc.js files. Moreover, with the newer version several new errors in ash/webui/camera_app_ui/ had to be fixed/suppressed. - Updated eslint-plugin-jsdoc from v37.5.1 to v46.8.2 to fix internal errors when running ESLint. - Replaced @typescript-eslint/sort-type-union-intersection-members with @typescript-eslint/sort-type-constituents (rule was renamed). - Removed jsdoc/newline-after-description rule (no longer exists) - Moved @typescript-eslint/prefer-optional-chain as needed in the .eslintrc.js file, since it now requires `parserOptions.project` to be specified for it to work. - Updated jsdoc/tag-lines rule definition, as needed to fix new errors (default spec for that rule seem to has changed) - Fixed newly found @typescript-eslint/prefer-nullish-coalescing violation. (Some ash/webui/camera_app_ui/ fixes provided by pihsun@) Bug: 1488690,b/303328674 Change-Id: I6667118a490b9177486d3cf90934ee43292eb1b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4910239 Reviewed-by: Joel Hockey <joelhockey@chromium.org> Reviewed-by: Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/main@{#1205440}
- Loading branch information
Showing
11 changed files
with
281 additions
and
357 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
ddc7cddc319ae5689ebf2c927e284814f2892e47 | ||
8fe0f8ea6861e4629e91aca59ea581f96a33fb91 |
Oops, something went wrong.