Activity

1. Marenz

   added

   part:❓We need to figure out which part is affectedWe need to figure out which part is affected

   priority:❓We need to figure out how soon this should be addressedWe need to figure out how soon this should be addressed

   type:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users

   on Feb 19, 2024
2. llucax commented on Feb 19, 2024

   

   llucax

   on Feb 19, 2024

   Contributor

   More actions

   I wonder if this could be useful for other teams, so if we should put it in api-common (if we make it directly a type of proto message) or base-client instead if we keep it as a python-only thing.

   @frequenz-floss/api-team does anyone envision having to use datetime ranges in other APIs? I guess for reporting if you are requesting data for a range you'll also have to specify a range, right?

   Reacted by nkrtzr and Christoph Wasicki
3. nkrtzr commented on Feb 20, 2024

   

   nkrtzr

   on Feb 20, 2024

   More actions

   @frequenz-floss/api-team does anyone envision having to use datetime ranges in other APIs? I guess for reporting if you are requesting data for a range you'll also have to specify a range, right?

   the weatehr client is using a list of datetime objects to specify the time of the forcasts to be filtered out.
   But for now a list with explicit timestamps is implemented. I'm not sure if ranges in combinations of ranges and timedeltas could be of interest for further development. What do you think @cwasicki?
4. llucax

   changed the title [-]add a DatetimeRange dataclass to pass pairs from/to.[/-] [+]Add a `DatetimeRange` dataclass to pass pairs from/to.[/+] on Feb 20, 2024
5. llucax

   changed the title [-]Add a `DatetimeRange` dataclass to pass pairs from/to.[/-] [+]Add a `DatetimeRange` dataclass to pass pairs from/to[/+] on Feb 20, 2024
6. cwasicki commented on Feb 21, 2024

   

   cwasicki

   on Feb 21, 2024

   More actions

   In my opinion for weather it can make sense to simplify the query to datetime ranges. Also, ranges are used in other APIs like reporting and I think trading.
7. Marenz

   added

   priority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the table

   scope:breaking-changeBreaking change, users will need to update their codeBreaking change, users will need to update their code

   and removed

   priority:❓We need to figure out how soon this should be addressedWe need to figure out how soon this should be addressed

   on Jun 21, 2024
8. llucax

   added

   part:clientAffects the client codeAffects the client code

   on Aug 29, 2024