chore(deps): update dependency eslint-plugin-vue to v8 #913
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#913
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/eslint-plugin-vue-8.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.20.0
->8.0.3
Release Notes
vuejs/eslint-plugin-vue
v8.0.3
Compare Source
🐛 Bug Fixes
It upgrade fixes the wrong location in multiple
<script>
Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v8.0.2...v8.0.3
v8.0.2
Compare Source
🐛 Bug Fixes
vue/multi-word-component-names
ruleFull Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v8.0.1...v8.0.2
v8.0.1
Compare Source
🐛 Bug Fixes
vue/valid-next-tick
rule.Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v8.0.0...v8.0.1
v8.0.0
Compare Source
💥 Breaking Changes
plugin:vue/vue3-essential
config.vue/no-deprecated-v-is
rule.vue/no-export-in-script-setup
rule.vue/valid-define-emits
rule.vue/valid-define-props
rule.vue/valid-next-tick
rule.vue/valid-v-memo
rule.vue/no-useless-template-attributes
rule.vue/no-computed-properties-in-data
rule.vue/multi-word-component-names
rule.vue/no-deprecated-router-link-tag-prop
rule.vue/no-reserved-props
rule.plugin:vue/vue3-strongly-recommended
config.vue/v-on-event-hyphenation
rule.vue/first-attribute-linebreak
rule.plugin:vue/vue3-recommended
config.plugin:vue/essential
config.vue/valid-next-tick
rule.vue/no-useless-template-attributes
rule.vue/no-computed-properties-in-data
rule.vue/multi-word-component-names
rule.vue/no-reserved-props
rule.plugin:vue/strongly-recommended
config.vue/first-attribute-linebreak
rule.plugin:vue/recommended
config.allowFirstLine
option of thevue/max-attributes-per-line
rule.✨ Enhancements
Core:
setup-compiler-macros
environment.Rules:
vue/first-attribute-linebreak
rule aims to enforce a consistent location for the first attribute.vue/no-reserved-props
rule that disallow reserved names to be used in props.vue/no-loss-of-precision
rule that appliesno-loss-of-precision
rule to expressions in<template>
.ignore
option tovue/multi-word-component-names
rule.asyncData
invue/no-dupe-keys
,vue/no-reserved-keys
,vue/no-template-shadow
,vue/no-undef-properties
, andvue/no-unused-properties
rules.🐛 Bug Fixes
vue/multi-word-component-names
rule.Full Changelog: https://github.com/vuejs/eslint-plugin-vue/compare/v7.20.0...v8.0.0
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
3c8385ae4c
to5a0c8216a5
5a0c8216a5
to6f06e7714d
6f06e7714d
to90f4a6d3f1
90f4a6d3f1
to64998e148e
64998e148e
to571e692b66
571e692b66
tofea452020f
fea452020f
tofbef9e5b20
I've disabled
vue/multi-word-component-names
for now and fixed the remaining few errors.