Request for clarification - futureSignal

[agreensh]

Say I have an initial future string

late final _futureString = futureSignal(() { return getAStringFromAnHttpRequest(); }, initialValue: '');
and the string is referenced/used, triggering the http load, why isn't the _futureString.value set to AsyncLoading, whereas if I do a _futureString.reload() (or .refresh()), it is? Surely in both cases, it is completing the future and should be in the AsyncLoading state?

How to tell if the initial future is being run without 2 tests (for isCompleted in the initial case, and AsyncLoading)?

[rodydavis]

If you are passing an initial string then you are giving it a non loading state to show instead.

You can always check to see if it is refreshing or loading with Async State.

Loading means there is not data, refreshing is updating existing data.

[agreensh]

But if I give an initial string, then isLoading, isRefreshing, isReloading are all false while it is getting the first "future" string.
If I reload, isReloading is true
If I refresh, isLoading and isRefreshing are true

So from having an initial string, to the setting of the value from the first "future" string (the return of the http request in my case) all of isLoading, isRefreshing and isReloading are false, so there is no way of knowing the future is being resolved? I would have thought it is being "refreshed" (from the initial value) during this time.

[rodydavis]

Interesting, I will make some test cases to check what the expected behavior should be!