Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 13, 2023

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: vuejs/eslint-plugin-vue@v9.8.0...v9.9.0

v9.8.0

✨ Enhancements

🐛 Bug Fixes

Full Changelog: vuejs/eslint-plugin-vue@v9.7.0...v9.8.0

v9.7.0

✨ Enhancements

⚙️ Updates

Full Changelog: vuejs/eslint-plugin-vue@v9.6.0...v9.7.0

v9.6.0

✨ Enhancements

... (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 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)

Bumps [eslint-plugin-vue](https://github.com/vuejs/eslint-plugin-vue) from 8.0.3 to 9.9.0.
- [Release notes](https://github.com/vuejs/eslint-plugin-vue/releases)
- [Commits](vuejs/eslint-plugin-vue@v8.0.3...v9.9.0)

---
updated-dependencies:
- dependency-name: eslint-plugin-vue
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 13, 2023
@pull-checklist
Copy link

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
Copy link

vercel bot commented Jan 13, 2023

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

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? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants