Add /month/week endpoint for TempService #484

Closed
opened 2026-04-21 14:47:54 +00:00 by a24timsv · 4 comments
Collaborator

Sub-issue of #20

Sub-issue of #20
Collaborator

I've completed this. I also updated the structure for /year and /month/year so they actually show temperatures and not HTTP 400 or 500 errors anymore.

Will do a pull request of this on Monday.

I've completed this. I also updated the structure for **/year** and **/month/year** so they actually show temperatures and not HTTP 400 or 500 errors anymore. Will do a pull request of this on Monday.
b24hugst added reference #484-weekly-aggregated-temperature 2026-04-24 14:30:34 +00:00
Author
Collaborator

I've been wondering something. Why exactly is the endpoint year/month/week? Seems rather weird to ask for a week within a month when a week can technically be a part of 2 months.

Then I looked at it again. Andras writes:

We need to have aggregated data under /year, /year/week ,/year/month

It is year/week and not year/month/week...

How is it built currently?

I've been wondering something. Why exactly is the endpoint year/month/week? Seems rather weird to ask for a week within a month when a week can technically be a part of 2 months. Then I looked at it again. Andras writes: > We need to have aggregated data under /year, /year/week ,/year/month It is year/week and not year/month/week... How is it built currently?
Collaborator

Haha yeah I noticed that too. I've done so it's /year/week 👍

Haha yeah I noticed that too. I've done so it's **/year/week** 👍
Author
Collaborator

Oh good. Great work!

Oh good. Great work!
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#484
No description provided.