You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have loading components that all use material-ui's LinearProgress, however they are all implemented differently.
Some declare a component and then return LinearProgress
We should centralize it so all components grab it from the same place and return the same loading component. This will make it easier if we ever wanted to change the component.
The text was updated successfully, but these errors were encountered:
We should make sure that we don't couple every loading state to a single loading component. I think we should have multiple centralized loading components for different use cases. i.e. routes shouldn't necessarily be using the same loading indicator as network retries
Currently we have loading components that all use material-ui's
LinearProgress
, however they are all implemented differently.Some declare a component and then return
LinearProgress
revelio/src/main/webapp/result-forms/route.js
Line 25 in 64373a2
and some just return
LinearProgress
directlyrevelio/src/main/webapp/user.js
Line 93 in 6f66f11
We should centralize it so all components grab it from the same place and return the same loading component. This will make it easier if we ever wanted to change the component.
The text was updated successfully, but these errors were encountered: