search

dgiot / iotStudio

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

chore(deps-dev): bump eslint from 6.8.0 to 8.22.0 #539

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps eslint from 6.8.0 to 8.22.0.

Release notes

Sourced from eslint's releases.

v8.22.0

Features

  • 2b97607 feat: Implement caching for FlatESLint (#16190) (Nicholas C. Zakas)
  • fd5d3d3 feat: add methodsIgnorePattern option to object-shorthand rule (#16185) (Milos Djermanovic)

Documentation

  • 9f5a752 docs: optimize image assets (#16170) (Sam Chen)
  • 61b2948 docs: add svgo command to pre commit hook (#16178) (Amaresh S M)
  • 784096d docs: improve search result UI (#16187) (Sam Chen)
  • d0f4cb4 docs: use shorthand property name in example (#16180) (Kevin Elliott)

Chores

  • 10a6e0e chore: remove deploy workflow for playground (#16186) (Milos Djermanovic)

v8.21.0

Features

  • 7b43ea1 feat: Implement FlatESLint (#16149) (Nicholas C. Zakas)
  • 92bf49a feat: improve the key width calculation in key-spacing rule (#16154) (Nitin Kumar)
  • c461542 feat: add new allowLineSeparatedGroups option to the sort-keys rule (#16138) (Nitin Kumar)
  • 1cdcbca feat: add deprecation warnings for legacy API in RuleTester (#16063) (Nitin Kumar)

Bug Fixes

  • 0396775 fix: lines-around-comment apply allowBlockStart for switch statements (#16153) (Nitin Kumar)

Documentation

  • 2aadc93 docs: add anchors to headings inside docs content (#16134) (Strek)

Chores

  • 8892511 chore: Upgrade to Espree 9.3.3 (#16173) (Brandon Mills)
  • 1233bee chore: switch to eslint-plugin-node's maintained fork (#16150) (唯然)
  • 97b95c0 chore: upgrade puppeteer v13 (#16151) (唯然)

v8.20.0

Features

Bug Fixes

  • 30be0ed fix: no-warning-comments rule escapes special RegEx characters in terms (#16090) (Lachlan Hunt)
  • bfe5e88 fix: ignore spacing before ] and } in comma-spacing (#16113) (Milos Djermanovic)

Documentation

  • 845c4f4 docs: Add website team details (#16115) (Nicholas C. Zakas)
  • 5a0dfdb docs: Link to blog post in no-constant-binary-expression (#16112) (Jordan Eldredge)
  • bc692a9 docs: remove install command (#16084) (Strek)
  • 49ca3f0 docs: don't show toc when content not found (#16095) (Amaresh S M)
  • ba19e3f docs: enhance 404 page UI (#16097) (Amaresh S M)
  • a75d3b4 docs: remove unused meta.docs.category field in working-with-rules page (#16109) (Brandon Scott)
  • cdc0206 docs: add formatters page edit link (#16094) (Amaresh S M)
  • 4d1ed22 docs: preselect default theme (#16098) (Strek)
  • 4b79612 docs: add missing correct/incorrect containers (#16087) (Milos Djermanovic)

... (truncated)

Changelog

Sourced from eslint's changelog.

v8.22.0 - August 13, 2022

  • 2b97607 feat: Implement caching for FlatESLint (#16190) (Nicholas C. Zakas)
  • fd5d3d3 feat: add methodsIgnorePattern option to object-shorthand rule (#16185) (Milos Djermanovic)
  • 9f5a752 docs: optimize image assets (#16170) (Sam Chen)
  • 61b2948 docs: add svgo command to pre commit hook (#16178) (Amaresh S M)
  • 784096d docs: improve search result UI (#16187) (Sam Chen)
  • d0f4cb4 docs: use shorthand property name in example (#16180) (Kevin Elliott)
  • 10a6e0e chore: remove deploy workflow for playground (#16186) (Milos Djermanovic)

v8.21.0 - August 1, 2022

  • 7b43ea1 feat: Implement FlatESLint (#16149) (Nicholas C. Zakas)
  • 8892511 chore: Upgrade to Espree 9.3.3 (#16173) (Brandon Mills)
  • 92bf49a feat: improve the key width calculation in key-spacing rule (#16154) (Nitin Kumar)
  • c461542 feat: add new allowLineSeparatedGroups option to the sort-keys rule (#16138) (Nitin Kumar)
  • 1cdcbca feat: add deprecation warnings for legacy API in RuleTester (#16063) (Nitin Kumar)
  • 0396775 fix: lines-around-comment apply allowBlockStart for switch statements (#16153) (Nitin Kumar)
  • 2aadc93 docs: add anchors to headings inside docs content (#16134) (Strek)
  • 1233bee chore: switch to eslint-plugin-node's maintained fork (#16150) (唯然)
  • 97b95c0 chore: upgrade puppeteer v13 (#16151) (唯然)

v8.20.0 - July 16, 2022

  • bbf8df4 chore: Mark autogenerated release blog post as draft (#16130) (Nicholas C. Zakas)
  • 845c4f4 docs: Add website team details (#16115) (Nicholas C. Zakas)
  • 5a0dfdb docs: Link to blog post in no-constant-binary-expression (#16112) (Jordan Eldredge)
  • bc692a9 docs: remove install command (#16084) (Strek)
  • 30be0ed fix: no-warning-comments rule escapes special RegEx characters in terms (#16090) (Lachlan Hunt)
  • ca83178 feat: catch preprocess errors (#16105) (JounQin)
  • 49ca3f0 docs: don't show toc when content not found (#16095) (Amaresh S M)
  • ba19e3f docs: enhance 404 page UI (#16097) (Amaresh S M)
  • bfe5e88 fix: ignore spacing before ] and } in comma-spacing (#16113) (Milos Djermanovic)
  • a75d3b4 docs: remove unused meta.docs.category field in working-with-rules page (#16109) (Brandon Scott)
  • cdc0206 docs: add formatters page edit link (#16094) (Amaresh S M)
  • 4d1ed22 docs: preselect default theme (#16098) (Strek)
  • 4b79612 docs: add missing correct/incorrect containers (#16087) (Milos Djermanovic)
  • 09f6acb docs: fix UI bug on rules index and details pages (#16082) (Deepshika S)
  • f5db264 docs: remove remaining duplicate rule descriptions (#16093) (Milos Djermanovic)
  • 32a6b2a docs: Add scroll behaviour smooth (#16056) (Amaresh S M)
  • eee4306 chore: update internal lint dependencies (#16088) (Bryan Mishkin)
  • 9615a42 chore: update formatter examples template to avoid markdown lint error (#16085) (Milos Djermanovic)
  • 62541ed chore: fix markdown linting error (#16083) (唯然)

v8.19.0 - July 1, 2022

  • 7023628 feat: add importNames support for patterns in no-restricted-imports (#16059) (Brandon Scott)
  • 472c368 feat: fix handling of blockless with statements in indent rule (#16068) (Milos Djermanovic)
  • fc81848 fix: throw helpful exception when rule has wrong return type (#16075) (Bryan Mishkin)
  • e884933 chore: use github-slugger for markdown anchors (#16067) (Strek)

... (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 2 years ago

Example Check Group #2 (Click here to edit)

vercel[bot] commented 2 years ago

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

Name Status Preview Updated
dgiot-dashboard ✅ Ready (Inspect) Visit Preview Aug 26, 2022 at 5:33AM (UTC)
pull-request-quantifier-deprecated[bot] commented 2 years 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.

dependabot[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.