docs(no-async-in-computed-properties): suggest computedAsync instead of vue-async-computed
#2976
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I accidentally stumbled upon the documentation page for no-async-in-computed-properties rule, and noticed that it suggests using vue-async-computed package in case we need async code in
computed. This package hasn't been maintained for over 2 years, so I believecomputedAsyncfrom VueUse is a much better, well-maintained alternative. Besides, there's a good chance that developers already use some other composable from VueUse, which means they won't need to install yet another random NPM package to solve a simple issue.