I see your point here. But: Usually, pending is used to e.g. provide placeholders or default content while the data is not there yet. As the data isn't there, pending is set to true. ☺️

Curious for suggestions/feedback

My suggestion is a new fetching property. It should be true only when the handler's promise is pending.

I've been exploring this idea in a module I'm working on, you can check it out in nuxt-query.

@manniL

Thank you for your answer, I think I misunderstood the meaning of pending.

But in documentation, the useAsyncData mentions that:
https://github.com/nuxt/framework/blob/dd56d36e3ea012d635daf22677086b8218f6e089/docs/content/1.docs/3.api/1.composables/use-async-data.md?plain=1#L64

According to the description here, I think the meaning is closer to fetching mentioned by @mahdiboomeri. Should we adjust the description of this property in the documentation?

I find the initial value of pending set to true confusing whenever I have the immediate: false.

@danielroe, would you consider it to be a bug? Should the immediate option impact the initial value of pending?

I also interpreted pending as meaning "loading" initially.

Let's say you want to display a loading spinner while the handler is being executed with immediate: false. You obviously don't want that spinner to be visible before the handler has been called, which will be the case if you condition the rendering of the spinner on pending.

Right now, there is no way to determine if the handler of the useAsyncData hook is loading. I tried achieving this with some wrapper around it, but I could think of nothing that wouldn't require changing the source of the original hook.

If the pending property is indeed working as the authors intended, then I think it should not be changed. But then I believe it would be useful to have a loading property that tells us if the handler function is being pending.

i had same issue and the only thing i did it is this

const {  data,  pending,  error,  refresh} = await useAsyncData(() => test(), {immediate: false});
pending.value = false;

in setup script. and it works!

My suggestion is a new fetching property. It should be true only when the handler's promise is pending.

I've been exploring this idea in a module I'm working on, you can check it out in nuxt-query.

Yes, indeed, I agree. pending is more like whether the data is fetched complete or not. act as the
vueuse useAsyncState isReady did , so we also need the isLoading property, @danielroe what do you think?
Or we can fix the pending is false when the immediate is false?

We decided to introduce a status property for more fine-grained control as pending is a mix-up of a few statuses here as discussed.

Closing this discussion here 👍🏻
Thanks everyone for your input

Follow-up on #18810