[x] 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) {
throw new Error('No more data')
}
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.