search

dgiot / iotStudio

dgiot平台行业应用扩展插件 dgiot for application plugin
https://dgiot-dashboard.vercel.app/
Mozilla Public License 2.0
282 stars 102 forks source link

chore(deps-dev): bump eslint from 6.8.0 to 8.35.0 #659

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps eslint from 6.8.0 to 8.35.0.

Release notes

Sourced from eslint's releases.

v8.35.0

Features

  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#16844) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#16826) (Daiki Nishikawa)

Bug Fixes

Documentation

  • f9f195e docs: Plugin docs cleanup & expansion (#16862) (Ben Perlmutter)
  • df809fd docs: Custom Formatters page cleanup/expansion (#16886) (Ben Perlmutter)
  • 0700d1b docs: Add PostCSS/Autoprefixer/CSSNano (#16502) (Nick Schonning)
  • 7b9e9bf docs: support unicode anchors (#16782) (Percy Ma)
  • 5fbc0bf docs: Update README (GitHub Actions Bot)
  • 67865a0 docs: Remove mention of mailing list (#16869) (Amaresh S M)
  • 43af24a docs: Add explanation of when to use 'warn' severity (#16882) (Nicholas C. Zakas)
  • ed2999b docs: Shareable configs page edits and expansion (#16824) (Ben Perlmutter)
  • 2780635 docs: fix typos (#16884) (Lioness100)
  • 5bdaae2 docs: Ways to Extend ESLint page (#16861) (Ben Perlmutter)

Chores

  • cdcbe12 chore: upgrade @​eslint/js@​8.35.0 (#16935) (Brandon Mills)
  • c954c34 chore: package.json update for @​eslint/js release (ESLint Jenkins)
  • 5a517da chore: package.json update for @​eslint/js release (ESLint Jenkins)
  • 9f10926 chore: upgrade @​eslint/eslintrc@​2.0.0 (#16928) (Milos Djermanovic)
  • da728fa ci: use LTS node version in workflows (#16907) (Nitin Kumar)
  • c57b4f3 perf: upgrade to esquery@1.4.2 (#16901) (Milos Djermanovic)
  • 9122f07 chore: Update stale bot settings (#16870) (Nicholas C. Zakas)

v8.34.0

Features

  • 9b2fcf7 feat: array-callback-return supports Array.prototype.toSorted (#16845) (SUZUKI Sosuke)

Bug Fixes

  • 923f61d fix: false positive with assignment in no-extra-parens (#16872) (Francesco Trotta)

Documentation

  • f0a9883 docs: split rules documentation (#16797) (Ben Perlmutter)
  • 67aa37b docs: fix typo in command-line-interface.md (#16871) (Kevin Rouchut)
  • 337f7ed docs: fix width of language input (#16849) (Tanuj Kanti)
  • 71349a1 docs: Configure a Parser page (#16803) (Ben Perlmutter)
  • de7e925 docs: remove extra line numbers in example (#16848) (jonz94)
  • ad38d77 docs: Update README (GitHub Actions Bot)

Chores

  • 9dbe06d chore: add type property to array-element-newline schema (#16877) (MHO)
  • a061527 chore: Remove unused functions (#16868) (Nicholas C. Zakas)

v8.33.0

... (truncated)

Changelog

Sourced from eslint's changelog.

v8.35.0 - February 26, 2023

  • cdcbe12 chore: upgrade @​eslint/js@​8.35.0 (#16935) (Brandon Mills)
  • c954c34 chore: package.json update for @​eslint/js release (ESLint Jenkins)
  • 5a517da chore: package.json update for @​eslint/js release (ESLint Jenkins)
  • 9f10926 chore: upgrade @​eslint/eslintrc@​2.0.0 (#16928) (Milos Djermanovic)
  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#16844) (Nicholas C. Zakas)
  • f9f195e docs: Plugin docs cleanup & expansion (#16862) (Ben Perlmutter)
  • df809fd docs: Custom Formatters page cleanup/expansion (#16886) (Ben Perlmutter)
  • 0700d1b docs: Add PostCSS/Autoprefixer/CSSNano (#16502) (Nick Schonning)
  • da728fa ci: use LTS node version in workflows (#16907) (Nitin Kumar)
  • 7b9e9bf docs: support unicode anchors (#16782) (Percy Ma)
  • 5fbc0bf docs: Update README (GitHub Actions Bot)
  • c57b4f3 perf: upgrade to esquery@1.4.2 (#16901) (Milos Djermanovic)
  • 9698bc5 fix: pin esquery v1.4.0 (fixes #16896) (#16897) (唯然)
  • 67865a0 docs: Remove mention of mailing list (#16869) (Amaresh S M)
  • 43af24a docs: Add explanation of when to use 'warn' severity (#16882) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#16826) (Daiki Nishikawa)
  • ed2999b docs: Shareable configs page edits and expansion (#16824) (Ben Perlmutter)
  • 2780635 docs: fix typos (#16884) (Lioness100)
  • 5bdaae2 docs: Ways to Extend ESLint page (#16861) (Ben Perlmutter)
  • 9122f07 chore: Update stale bot settings (#16870) (Nicholas C. Zakas)

v8.34.0 - February 10, 2023

  • f0a9883 docs: split rules documentation (#16797) (Ben Perlmutter)
  • 923f61d fix: false positive with assignment in no-extra-parens (#16872) (Francesco Trotta)
  • 9dbe06d chore: add type property to array-element-newline schema (#16877) (MHO)
  • a061527 chore: Remove unused functions (#16868) (Nicholas C. Zakas)
  • 67aa37b docs: fix typo in command-line-interface.md (#16871) (Kevin Rouchut)
  • 337f7ed docs: fix width of language input (#16849) (Tanuj Kanti)
  • 9b2fcf7 feat: array-callback-return supports Array.prototype.toSorted (#16845) (SUZUKI Sosuke)
  • 71349a1 docs: Configure a Parser page (#16803) (Ben Perlmutter)
  • de7e925 docs: remove extra line numbers in example (#16848) (jonz94)
  • ad38d77 docs: Update README (GitHub Actions Bot)

v8.33.0 - January 28, 2023

  • 17f4be2 docs: Fix examples in no-multiple-empty-lines rule (#16835) (jonz94)
  • 9c7cfe3 docs: 'Source Code' content in 'Set up Development Environment' page (#16780) (Ben Perlmutter)
  • ede5c64 docs: Custom processors page (#16802) (Ben Perlmutter)
  • 2620614 docs: Code of Conduct page (#16781) (Ben Perlmutter)
  • 50a8efd docs: report a sec vulnerability page (#16808) (Ben Perlmutter)
  • 2cc7954 feat: add restrictDefaultExports option to no-restricted-exports rule (#16785) (Nitin Kumar)
  • ed60afd docs: Update page titles, section landing pages, and side TOC (#16760) (Ben Perlmutter)
  • 333c712 docs: add background to code-path-diagrams for dark-mode (#16822) (Tanuj Kanti)
  • f5f7b9b docs: Update README (GitHub Actions Bot)
  • 2aa4f5f docs: no-constant-condition: Add multi-comparison example (#16776) (Sebastian Simon)
  • 40287db docs: Remove Google Group icon (#16779) (Nicholas C. Zakas)

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
pull-checklist[bot] commented 1 year ago

Example Check Group #2 (Click here to edit)

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
dgiot-dashboard ❌ Failed (Inspect) Feb 27, 2023 at 6:03AM (UTC)
pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.