asgrim/year

API responds with outdated information

andrew-demb opened this issue · 2 comments

andrew-demb commented

Now is 2024 in my calendar, but "en/currentYear" responds with 2023

asgrim commented

I agree. This is problematic for everyone. I think the fix is very complex though, it might take a few months to resolve

  • 👍2
andrew-demb commented

I will add a hacky workaround on my side.

Waiting for the fix, thank you

  • 👍2