Closed anthonydillon closed 3 years ago
We have several design for the loading and empty states, but I remember @hatched wanted to see how the new watcher behaved (correct me if I’m wrong, Jeff). Not sure, but might be worth implementing a loading or empty message state anyway?
Yes @clagom I still feel like we shouldn't implement those designs as the new watcher will be coming in the near future.
This is interesting multi-step problem...
Because of this process I feel like we should start without any tables rendered and instead..
Yeah, this issue is about the initial render of the application and not the update life cycle. I agree 1 and 2 suggestions.
Not sure about 4. I would say if it's reasonably "live" we just present the data and the user can be confident it's up to date. If something noteworthy occurs like a model moves to error state we should provide notifications for that.
We have spinners for loading, and no information design in progress.
Describe the bug When you first open the app it takes a while to populate the model data. In this time there is no user feedback and the three tables is strange without content.
Expected behavior I would expect this to vote to work like MAAS and only display a status table once there is content for it. If no models are available the application should say so.