Skip to content

[BUG] Error thrown when no more data to fetch #372

@adeacetis

Description

@adeacetis
  • I checked my browser's console output for errors and included it in the issue if any

image

  • I have attached an export of my aggr database in the issue
    NA
  • I documented the issue with screenshots
  • 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')
}

Of course, if the service fails it should throw.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions