Add /month/week endpoint for TempService #484

New issue

Closed

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

a24timsv commented

2026-04-21 14:47:54 +00:00

Collaborator

Sub-issue of #20

a24timsv added the

enhancement

backEnd

labels

2026-04-21 14:47:54 +00:00

b24hugst was assigned by a24timsv

2026-04-21 14:47:54 +00:00

b24hugst commented

2026-04-24 14:27:25 +00:00

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

a24timsv commented

2026-04-24 14:32:39 +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?

b24hugst commented

2026-04-24 14:33:38 +00:00

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** 👍

a24timsv commented

2026-04-24 14:36:48 +00:00

Author

Collaborator

Oh good. Great work!

b24hugst referenced this issue

2026-04-27 10:23:57 +00:00