status field to distinguish pending vs. loading?

[bdrazen]

Just curious if there was a consideration at any point towards possibly splitting the current pending status into loading and a fourth one denoting the inverse (isPending && !isFetching)? Maybe nascent or something? Had a lot of code throughout a project that relied on the status field passed as a prop to downstream components that I was forced to completely refactor since status alone could no longer reflect isLoading as it did in the original version. At least with two distinct statuses you could cover all bases: status === 'nascent', status === 'loading', ['nascent', 'loading'].includes(status). As it stands, the field has been rendered virtually useless in my project and am not even sure of its intended use case any longer over the boolean flags (isLoading, isPending, etc.).

[abhayclasher]

yo, i feel u. the v5 naming shift from loading to pending tripped up a lot of devs.

tbh the reason they split it is to separate the data state (status) from the network state (fetchStatus).

if u miss the old loading behavior, u basically want isPending && isFetching. query actually exports an isLoading boolean exactly for this (initial fetch with no data yet).

if u really need a single string field for downstream props, u might have to just wrap the hook and derive a custom status like nascent yourself. but sticking to the booleans is usually the 'meta' way now since it handles all the edge cases better. ✌️

[bdrazen]

Yeah, I'm aware of isLoading. Just saying it leads me to basically fully abandon status in favor of those boolean flags across my entire project. I ended up writing a convenience function that returns my suggested breakdown from a QueryResult in cases where I needed a single prop but it's far from ideal. Wondering if some kind of new field (maybe state) that granularizes the pending could be a reasonable addition without breaking compat.

Edit: Wow, just realized v2 actually broke status down in exactly this way with idle but got clobbered together in v4, then renamed in v5. Still kinda wish there were at least a separate field that preserves the original breakdown. Having to either pass down both status and fetchStatus or filter through some custom util is very clunky.