2.0 - Retrying state distinct from Loading/Errored/isPending?

[rvlzzr]

Scenario	Solid 2.0 Primitive
First load	<Loading>
Stale while revalidate	isPending()
Error occurred	<Errored>
Error retry or evict+refetch in progress	❌ Nothing

Solid 2.0 appears to provide no built-in primitive for detecting when a previously failed (or explicitly evicted) value is being fetched again without a stale value to show.

Specifically:

• Inside <Errored fallback={(err, reset) => ...}>, calling reset() triggers recomputation but returns immediately; there is no promise, signal, or observable retry state exposed to the fallback.

• After a cache eviction + re-read, there is no isPending(...)-equivalent for the case where the previous value is gone and a new fetch is now in flight.

This means retry/refetch UI currently requires manual coordination, such as managing an isRetrying signal and wiring it to prefetch(...).finally(...) alongside reset().

Should Solid expose something for this case, such as:

• an isRetrying(...) / isRefetching(...) primitive, or
• a reset() API that returns a promise or observable retry lifecycle?