Kirill Ivanov

yep  

related, but seems more general: https://github.com/blockscout/blockscout-rs/issues/514

Caveat: chart "ActiveAccounts". Adding intervals requires us to calculate/store unique users for each interval. It's quite non-trivial. Also not really clear what to do with cumulative/increasing graphs. Show result at...

Almost forgot: graphs with averages are non-trivial as well. To properly compute an average of some interval from averages of subintervals we need to retrieve # of entries for each...

for now will implement it for easier cases, let's decide on "ActiveAccounts" later..

> Also not really clear what to do with cumulative/increasing graphs. Show result at the start/middle/end of the interval, or even an average value. and for this it makes sense...

## API design (report-ish) ### Request Add a parameter to query string (enum => string with some set of available values). Variants: - day - week - month - year...

some other rejected variants: - separate types for each resolutions in response => sounds hard to abstract on frontend side (need to support each type separately) + weeks are non-trivial...

@ganzr as the message says, you also need `protoc-gen-openapiv2` (probably version `v2.19.0` at the time of writing this response) to build the crate