chore(deps-dev): bump eslint-plugin-vue from 8.0.3 to 9.9.0

[dependabot[bot]]

Bumps eslint-plugin-vue from 8.0.3 to 9.9.0.

Release notes

Sourced from eslint-plugin-vue's releases.

v9.9.0

✨ Enhancements

• #2066 Added vue/array-element-newline rule that applies the core array-element-newline rule to expressions in \<template>.
• #2042 Improved vue/script-indent rule to support more TypeScript syntax.
• #2052 Added vue/padding-lines-in-component-definition rule that requires or disallows padding lines in component definition.
• #2068 Added new ATTR_DYNAMIC, ATTR_STATIC, and ATTR_SHORTHAND_BOOL options to vue/attributes-order rule.

🐛 Bug Fixes

• #2069 Fixed false positive for type-only imports in vue/component-name-in-template-casing rule.
• #2070 Fixed spaces around comma in vue/component-api-style rule report messages.
• #2071 Fixed vue/define-macros-order rule to hoist secondary expressions correctly.
• #2073 Fixed false positives for circular references in <script setup> in vue/no-undef-components rule.

Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v9.8.0...v9.9.0

v9.8.0

✨ Enhancements

• #2019 Added vue/require-prop-comment rule that requires props to have a comment.
• #2034 Added suggestion for vue/require-name-property rule.

🐛 Bug Fixes

• #2024 Fixed false positives for <Textarea> components in vue/no-textarea-mustache rule.
• #2040 Fixed false positives for exported interfaces/type declarations in vue/define-macros-order rule.
• #2031 Fixed false positives for HTML tags when using HTML-like components in vue/component-name-in-template-casing rule.
• #2045 Fixed vue/attribute-hyphenation rule to disable autofix for attributes containing underscores (_).

Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v9.7.0...v9.8.0

v9.7.0

✨ Enhancements

• #1996 Added vue/multiline-ternary rule that applies the core multiline-ternary rule to expressions in \<template> and <style>.
• #2009 Added vue/v-on-handler-style rule that enforces writing style for handlers in v-on directives.
• #1989 Added globals option to vue/component-name-in-template-casing rule.
• #2013 Added support for regexp options to vue/no-restricted-class rule.

⚙️ Updates

• #2009 Deprecated vue/v-on-function-call rule. Use the new vue/v-on-handler-style rule instead.

Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v9.6.0...v9.7.0

v9.6.0

✨ Enhancements

• #1943 Added vue/no-required-prop-with-default rule that enforces props with default values ​​to be optional.

... (truncated)

Commits

• 487a71c 9.9.0
• 0b816dc Add new attributes order for dynamic and static props (#2068)
• ad07deb Fix false positives for circular references in <script setup> in `vue/no-unde...
• 5e0bd2c Add padding-lines-in-component-definition rule (#2052)
• abdd93d fix (vue/define-macros-order): hoist secondary expressions correctly (#2071)
• 2c3d623 test (vue/max-attributes-per-line): add test for max value as object (#2072)
• d339e2e fix (vue/component-api-style): add spacing around comma in report message (#2...
• 4a08c07 fix: [vue/component-name-in-template-casing] False positive for dynamic compo...
• e42f737 Improve indent rule to support more ts syntax (#2042)
• 89fb2fe Added array-element-newline rule from eslint (#2066)
• Additional commits viewable in compare view

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]]

Example Check Group #2 (Click here to edit)

• [ ] Modify this checklist and click on the save button for it to appear on Github Pull Requests for this repo
• [ ] If you would like the checklist state to roll up to the Pull Request status, select the Enforce on Merge checkbox

[vercel[bot]]

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

Name	Status	Preview	Updated
dgiot-dashboard	❌ Failed (Inspect)		Jan 13, 2023 at 5:08AM (UTC)

[pull-request-quantifier-deprecated[bot]]

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.

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
  • 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 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.