My goal: A table that shows a single loading graphic when its backing query is loading.
Issue: I get two overlapping icons. If I enable "Hoist loading state" in the parent container, one of the two icons changes to a different style (?). I can't seem to get just one loading icon.
Steps I've taken to troubleshoot: I've looked for documentation on loading state, table loading state, hoist loading state, but didn't find any. I saw some posts here but nothing fruitful.
Additional info: (Cloud or Self-hosted, Screenshots)
Self-hosted, Retool version 3.178.0
I'm sure I'm missing something trivial, but am not sure what to look for (since there doesn't seem to be documentation on this feature). My layout is basic: a container with a table inside it, and the table has a DB query as its data. When I run the query, I get two spinners. What should I look at to troubleshoot?
I haven't been able to replicate this, as in I only get one spinner, both when using hoist loading state and when not using it.
The only way I was able to replicate this is when I add a {{ query4.isFetching }} to the "loading" setting of my container. However if I enable hoist loading state that goes away.
Do you see both spinners in all the below combinations?
No hoisting and no loading settings
No hoisting but loading settings in the container
Hoisting and loading settings
Hoisting without loading settings
If so, another useful thing would be to see what other components doe syour query updates:
@MiguelOrtiz Thank you for digging in with me. I tried to capture a video, but with the 4MB upload limit it's hard to capture it well.
I've tested all combinations of hoisting (yes/no hoist) and loading (blank or getCollections.isFetching). In all cases I get double loading spinners. The only difference is:
With hoist=yes OR loading=getCollections.isFetching, the two spinners have different look and feel (exhibit A)
With hoist=no AND loading=blank, the two spinners are identical but slightly offset (exhibit B)
Maybe the styles give a hint where the duplicate is coming from? They're slightly offset from each other, but both roughly centered on the table.
I've confirmed that my query only updates one thing, collections.data (collections is my table). It is controlled BY another query, but even when I delete that relationship the loading behavior persists.