useFetch/useAsyncData status is success for a split second before changing to pending

[RifatMahmudno-1]

useFetch/useAsyncData status is success for a split second before changing to pending

[manniL]

@sebaguse Will cause the same problem from V4 on as it will rely on status. see #25864

[manniL]

My guess: It is success at first because data exists already (was previously fetched), then the fetching is triggered again. You can double-check that if you add a new Date() to the API response.

I agree that it isn't convenient/it is confusing.

(cc @danielroe wdyt?)

[RifatMahmudno-1]

Let's say I want to show a loading placeholder until the status is success and don't want to display the old data. So, in current condition, it will first render old data, then render the loading placeholder and then get the new data and then will render it. Which is a problem. Will it be fixed or there is another way of doing it?

[sebaguse]

what about using pending for a placeholder instead of status, would that work?

[RifatMahmudno-1]

what about using pending for a placeholder instead of status, would that work?

Doesn't work. When status is idle or pending then pending is true. When status is success or error then pending is false. So, the behavior will be similar. Pending will be false for a split second => true => false.