Why not give us a recommended solution in Docs for loading error and resolved promises?

[louiss0]

Adding Promised to Core or Just Documenting Promise.

I'm here to talk about A component called <Promised/> from Vue promised. I believe it should either be added to core or be used as the recommend solution for Handling Promises. Why? Handling promises is simple in Vue and does not require any specific tooling for simple stuff. But dealing with them is more complicated than just using an if or else statement. There are other things developers have to think about that they won't understand until it's too late. By the time they do, they will most likely implement their own solution.

The idea of having a unified Promised-based solution is one that people want. There was an article # On Escape's Vue 2 to Svelte Migration that was written a while back about Vue not having good solutions to basic problems one of them was a Promise handling solution.

[!Warning] Your answer was

Vue does not have a built-in for handling Promise state directly in the template, but this can be easily achieved with libraries such as vue-promised.

I understand that you want to make Vue more performant as a framework and adding more libraries makes the framework a lot smaller in bundle size. But having a declarative Promise handling solution is a well need thing. Svelte Flutter Riverpod and Qwik each have their own way of doing this. They also decided to put their solutions in their respective documentation's.

• Qwik: Resource
• Flutter Riverpod: Future Provider

I know that suspense exists but it does not handle pending and it seems like there is no intention to handle errors. It could though. Suspense Loading State

The point I'm trying to make here is that I believe there should be either an in-built solution that handles loading error and resolved states or vue-promised should be the recommended solution. Developers don't want to have to handle this problem on their own. They want an in-built or an official solution. I hope this is enough for you.