From 02dfb926af442da86c2b253408008bcb4ca7a2bf Mon Sep 17 00:00:00 2001 From: Shayan Zamani Date: Wed, 26 Nov 2025 21:01:35 +0330 Subject: [PATCH 1/2] docs: fix minor grammatical issues --- docs/rules/no-async-in-computed-properties.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/rules/no-async-in-computed-properties.md b/docs/rules/no-async-in-computed-properties.md index ff4f18d78..ff2ddc781 100644 --- a/docs/rules/no-async-in-computed-properties.md +++ b/docs/rules/no-async-in-computed-properties.md @@ -12,8 +12,8 @@ since: v3.8.0 - :gear: This rule is included in all of `"plugin:vue/essential"`, `*.configs["flat/essential"]`, `"plugin:vue/vue2-essential"`, `*.configs["flat/vue2-essential"]`, `"plugin:vue/strongly-recommended"`, `*.configs["flat/strongly-recommended"]`, `"plugin:vue/vue2-strongly-recommended"`, `*.configs["flat/vue2-strongly-recommended"]`, `"plugin:vue/recommended"`, `*.configs["flat/recommended"]`, `"plugin:vue/vue2-recommended"` and `*.configs["flat/vue2-recommended"]`. -Computed properties and functions should be synchronous. Asynchronous actions inside them may not work as expected and can lead to an unexpected behaviour, that's why you should avoid them. -If you need async computed properties you might want to consider using additional plugin [vue-async-computed] +Computed properties and functions should be synchronous. Asynchronous actions inside them may not work as expected and can lead to unexpected behaviour; that's why you should avoid them. +If you need async computed properties, you might want to consider using an additional plugin such as [vue-async-computed] ## :book: Rule Details From 7024026d16d0a663926c74119299b28a9d74a41f Mon Sep 17 00:00:00 2001 From: Shayan Zamani Date: Wed, 26 Nov 2025 21:08:20 +0330 Subject: [PATCH 2/2] docs: suggest `computedAsync` instead of 'vue-async-computed' --- docs/rules/no-async-in-computed-properties.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/rules/no-async-in-computed-properties.md b/docs/rules/no-async-in-computed-properties.md index ff2ddc781..0053adbbe 100644 --- a/docs/rules/no-async-in-computed-properties.md +++ b/docs/rules/no-async-in-computed-properties.md @@ -13,7 +13,7 @@ since: v3.8.0 - :gear: This rule is included in all of `"plugin:vue/essential"`, `*.configs["flat/essential"]`, `"plugin:vue/vue2-essential"`, `*.configs["flat/vue2-essential"]`, `"plugin:vue/strongly-recommended"`, `*.configs["flat/strongly-recommended"]`, `"plugin:vue/vue2-strongly-recommended"`, `*.configs["flat/vue2-strongly-recommended"]`, `"plugin:vue/recommended"`, `*.configs["flat/recommended"]`, `"plugin:vue/vue2-recommended"` and `*.configs["flat/vue2-recommended"]`. Computed properties and functions should be synchronous. Asynchronous actions inside them may not work as expected and can lead to unexpected behaviour; that's why you should avoid them. -If you need async computed properties, you might want to consider using an additional plugin such as [vue-async-computed] +If you need async computed properties, consider using the [`computedAsync`] composable from VueUse. ## :book: Rule Details @@ -147,9 +147,9 @@ const fetchData = computed(() => { ## :books: Further Reading -- [vue-async-computed] +- [`computedAsync`] -[vue-async-computed]: https://github.com/foxbenjaminfox/vue-async-computed +[`computedAsync`]: https://vueuse.org/core/computedAsync ## :rocket: Version