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

dependabot[bot] commented 1 year ago

Bumps eslint-plugin-vue from 8.0.3 to 9.8.0.

Release notes

Sourced from eslint-plugin-vue's releases.

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

#1982 Added consistent option to vue/padding-line-between-tags rule.

🐛 Bug Fixes

#1988 Fixed false positives for uninitialized vars in vue/no-ref-as-operand rule.

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

v9.5.1

🐛 Bug Fixes

#1976 Fixed false positives for <script setup> with TypeScript in vue/no-undef-components rule.

Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v9.5.0...v9.5.1

v9.5.0

✨ Enhancements

... (truncated)

Commits

a15d036 9.8.0
ec0276b Disable autofix in vue/attribute-hyphenation for attributes with underscore...
ced6fc3 Chore: add script to site that remove service-worker (#2047)
2d46741 Ignore well known tags in component-name-in-template-casing (#2031)
0fd431e Chore: fix playground (#2046)
55daf43 Chore: use vitepress instead of vuepress (#2044)
1d669d3 fix(docs): update example code for watch() (#2041)
8dc3cd9 fix(define-macros-order): update rule to support interface/type export in <sc...
cc1b8d9 feat: rule fixer for require-name-property (#2034)
9673a61 docs: fix formatting and grammar for clarity (#2028)
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] commented 1 year ago

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] commented 1 year ago

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

Name	Status	Preview	Updated
dgiot-dashboard	❌ Failed (Inspect)		Nov 28, 2022 at 5:10AM (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.

dependabot[bot] commented 1 year ago

Superseded by #648.

dgiot / iotStudio

chore(deps-dev): bump eslint-plugin-vue from 8.0.3 to 9.8.0 #636

v9.8.0

✨ Enhancements

🐛 Bug Fixes

v9.7.0

✨ Enhancements

⚙️ Updates

v9.6.0

✨ Enhancements

🐛 Bug Fixes

v9.5.1

🐛 Bug Fixes

v9.5.0

✨ Enhancements

Example Check Group #2 (Click here to edit)