Dashboard API Timeouts, Tries and Intervals #6
Description
When a user is in their dashboard there should be logic that populates their DOM with some kind of persistent data that wont change about their portfolio: crypto name, icon, the bootstrap element the data lives in etc.
API calls should be made in 1 minute intervals for price data and 5 minute intervals for candle updates. And the user shouldn't have to lose all their DOM elements if the API hits a 429 error.
-loading gifs and opacity layer should populate if the user is waiting for an API call
-if a call gets a 429 error: try-catch logic should set a wait interval to request again in 20second - 1 minute intervals