Skip to content

Commit

Permalink
9.16.0
Browse files Browse the repository at this point in the history
  • Loading branch information
ota-meshi committed Jul 29, 2023
1 parent 684c847 commit 56180e3
Show file tree
Hide file tree
Showing 5 changed files with 21 additions and 6 deletions.
6 changes: 5 additions & 1 deletion docs/rules/block-order.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@ pageClass: rule-details
sidebarDepth: 0
title: vue/block-order
description: enforce order of component top-level elements
since: v9.16.0
---
# vue/block-order

> enforce order of component top-level elements
- :exclamation: <badge text="This rule has not been released yet." vertical="middle" type="error"> ***This rule has not been released yet.*** </badge>
- :wrench: The `--fix` option on the [command line](https://eslint.org/docs/user-guide/command-line-interface#fixing-problems) can automatically fix some of the problems reported by this rule.

## :book: Rule Details
Expand Down Expand Up @@ -188,6 +188,10 @@ This rule warns about the order of the top-level tags, such as `<script>`, `<tem

- [Style guide - Single-file component top-level element order](https://vuejs.org/style-guide/rules-recommended.html#single-file-component-top-level-element-order)

## :rocket: Version

This rule was introduced in eslint-plugin-vue v9.16.0

## :mag: Implementation

- [Rule source](https://github.com/vuejs/eslint-plugin-vue/blob/master/lib/rules/block-order.js)
Expand Down
6 changes: 5 additions & 1 deletion docs/rules/no-deprecated-model-definition.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@ pageClass: rule-details
sidebarDepth: 0
title: vue/no-deprecated-model-definition
description: disallow deprecated `model` definition (in Vue.js 3.0.0+)
since: v9.16.0
---
# vue/no-deprecated-model-definition

> disallow deprecated `model` definition (in Vue.js 3.0.0+)
- :exclamation: <badge text="This rule has not been released yet." vertical="middle" type="error"> ***This rule has not been released yet.*** </badge>
- :bulb: Some problems reported by this rule are manually fixable by editor [suggestions](https://eslint.org/docs/developer-guide/working-with-rules#providing-suggestions).

## :book: Rule Details
Expand Down Expand Up @@ -70,6 +70,10 @@ export default defineComponent({

- [Migration Guide – `v-model`](https://v3-migration.vuejs.org/breaking-changes/v-model.html)

## :rocket: Version

This rule was introduced in eslint-plugin-vue v9.16.0

## :mag: Implementation

- [Rule source](https://github.com/vuejs/eslint-plugin-vue/blob/master/lib/rules/no-deprecated-model-definition.js)
Expand Down
7 changes: 5 additions & 2 deletions docs/rules/no-use-v-else-with-v-for.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,12 @@ pageClass: rule-details
sidebarDepth: 0
title: vue/no-use-v-else-with-v-for
description: disallow using `v-else-if`/`v-else` on the same element as `v-for`
since: v9.16.0
---
# vue/no-use-v-else-with-v-for

> disallow using `v-else-if`/`v-else` on the same element as `v-for`
- :exclamation: <badge text="This rule has not been released yet." vertical="middle" type="error"> ***This rule has not been released yet.*** </badge>

## :book: Rule Details

This rule reports elements that have both `v-else-if`/`v-else` and `v-for` directives. That is valid in Vue (`v-else-if`/`v-else` will take precedence), but is confusing to read.
Expand Down Expand Up @@ -48,6 +47,10 @@ If you don't find using `v-else-if`/`v-else` together with `v-for` confusing to

- [vue/no-use-v-if-with-v-for](./no-use-v-if-with-v-for.md)

## :rocket: Version

This rule was introduced in eslint-plugin-vue v9.16.0

## :mag: Implementation

- [Rule source](https://github.com/vuejs/eslint-plugin-vue/blob/master/lib/rules/no-use-v-else-with-v-for.js)
Expand Down
6 changes: 5 additions & 1 deletion docs/rules/require-typed-object-prop.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@ pageClass: rule-details
sidebarDepth: 0
title: vue/require-typed-object-prop
description: enforce adding type declarations to object props
since: v9.16.0
---
# vue/require-typed-object-prop

> enforce adding type declarations to object props
- :exclamation: <badge text="This rule has not been released yet." vertical="middle" type="error"> ***This rule has not been released yet.*** </badge>
- :bulb: Some problems reported by this rule are manually fixable by editor [suggestions](https://eslint.org/docs/developer-guide/working-with-rules#providing-suggestions).

## :book: Rule Details
Expand Down Expand Up @@ -44,6 +44,10 @@ Nothing.

When you're not using TypeScript in the project.

## :rocket: Version

This rule was introduced in eslint-plugin-vue v9.16.0

## :mag: Implementation

- [Rule source](https://github.com/vuejs/eslint-plugin-vue/blob/master/lib/rules/require-typed-object-prop.js)
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "eslint-plugin-vue",
"version": "9.15.1",
"version": "9.16.0",
"description": "Official ESLint plugin for Vue.js",
"main": "lib/index.js",
"scripts": {
Expand Down

0 comments on commit 56180e3

Please sign in to comment.