Can't tell whether `isLoading` is caused by auto-refresh or call to `refresh` about redux-autoloader HOT 2 OPEN

You are very right, the terms are confusing. It's clearly an oversight from me.

The first thing that probably should be done would be to remove the confusion between "reload" and "refresh" as they mean essentially the same. However, if "autoRefreshing" was called "autoReloading", it would be misleading as there could still be automatic reloads based on other options (reload or reinitialize). Thus, I think autoRefreshing should be simply renamed to polling.

Let me try to make more sense out of the naming by virtually renaming some of the options and props:

options

props

I can't figure out how the wrapped component could separate the two cases when looking at the props redux-autoloader is passing.

From the new prop names it might be more clear that the library doesn't currently keep state of how the loading (->isLoading) was triggered. With this implementation it is not possible to know the source; whether it was because of polling, manual reload or a lifecycle reload.

Clearly the isRefreshing is the most misleading here, as it should had originally been named as isAutoRefreshing.

from redux-autoloader.

Great suggestion for the name changes imo!

However, the main reason I opened the ticket was that I needed (and I still need) a way to distinguish the different reasons for the loading. I have a view where I use polling to keep the data fresh but the data in the view could also change due to a user-invoked async operation, in which case I want to show a loader until the data is up-to-date again. Could you add support for that?

from redux-autoloader.