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
MetastaleUsed to mark issues that were closed for being staleTeam:CoreCore services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
The design team needs someone to convert the existing status / error / loading pages to React. We can help with the styling and usage of EUI components to make it look pretty, but everything should already be provided in EUI for that part.
Specifically with the loading page (the big circle) it would be nice to have some sort of string to designate the app/plugin that is loading. This way we can tailor the load a little different for each app.
I'm not sure if the loading page between apps can realistically use react for the legacy platform stuff (which is all current apps). The whole reason the loading page appears in the first place is that our bundles are large enough to take a non-trivial amount of time to load, so we show a loading indicator while the network requests are in flight to load the CSS/JS. We do this by coding all of the markup and styles for the loading indicator directly into the html payload and then removing them when the bundles finish loading.
This will be different in the new platform apps, where the loading indicator will happen within the context of the chrome rather than as a whole page refresh.
Either way, I do think we could inject the app name into the loading message, but I think we need a solution that can still be embedded entirely in the html payload.
MetastaleUsed to mark issues that were closed for being staleTeam:CoreCore services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
The design team needs someone to convert the existing status / error / loading pages to React. We can help with the styling and usage of EUI components to make it look pretty, but everything should already be provided in EUI for that part.
Specifically with the loading page (the big circle) it would be nice to have some sort of string to designate the app/plugin that is loading. This way we can tailor the load a little different for each app.
cc @epixa
The text was updated successfully, but these errors were encountered: