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
I provided a clear and concise description of what the bug is (see both sections below)
HistoricalService is currently throwing an error when it reaches the end of the fetched data's range.
The desired behavior is for the HistoricalService to notify the user when it has fetched all available data and is stopping, instead of throwing an error.
if(!json.results.length){thrownewError('No more data')}
Of course, if the service fails it should throw.
The text was updated successfully, but these errors were encountered:
NA
HistoricalService is currently throwing an error when it reaches the end of the fetched data's range.
The desired behavior is for the HistoricalService to notify the user when it has fetched all available data and is stopping, instead of throwing an error.
Of course, if the service fails it should throw.
The text was updated successfully, but these errors were encountered: