Guys,
When I open a specific page in my app, my browser render some elements (text elements that appears as “This is some text”, image that appears as broken links, etc) before fetching the collections and only then it refreshes after retrieving the results from my backend.
It works but it is not a great user experience.
Any workarounds on this?
You can use the isFetching property on your collections to display conditionally the content, or you can use the nullish coalescent operator to fall back to a different value. If you wanted to fall back to an empty string, you simply could do something like this: [your_property].value ?? "" or I (this one is not confirmed, I’d need to test it) the state “This is some text” is what you wrote inside before binding, so in theory if you want to display something else, it could be a workaround as well to use this logic.
The solution using the isFetched worked.
Just had to put everything inside a container element with a conditional display using that approach.
Hi Broberto,
I’ll open this thread here again.
I have an auth-protected page that people are redirected to after login and where data is loaded from Xano.
Regarding the conditional rendering based on isFetching property of a collection: Should I set the data query in WeWeb’s Data Collection tab to Fetch Automatically (“fetch this collection automatically”) or should I trigger the fetching within the login workflow and then initiate the page change?