You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In calendar widget current year defined with standard function time.ISOWeak(). And as written in documentation
// ISOWeek returns the ISO 8601 year and week number in which t occurs.// Week ranges from 1 to 53. Jan 01 to Jan 03 of year n might belong to// week 52 or 53 of year n-1, and Dec 29 to Dec 31 might belong to week 1// of year n+1.func (tTime) ISOWeek() (year, weekint){}
last days of December every year will produce year n+1 not n.
Thats what i got with date December 30,2024
Do we need to change time.ISOWeak() to time.Now().Date() or not?
Also i'm resolving conflicts of PR #174 now, which involves calendar events. And the change to time.Now().Date() ensure if someone has events during the New Year's holiday, they will see them in the widget.
Happy New Year 🎉🎉🥳
The text was updated successfully, but these errors were encountered:
Oh my, thanks for reporting this! 😅 I'm in the process of moving the calendar rendering and logic to the front-end since a bunch of people have public instances of Glance and it doesn't make sense for the calendar time to be based on the server time. Presumably this behavior is also present in JS, I'll keep it in mind and try to resolve it.
What's the point
In calendar widget current year defined with standard function
time.ISOWeak()
. And as written in documentationlast days of December every year will produce year
n+1
notn
.Thats what i got with date December 30,2024
Do we need to change
time.ISOWeak()
totime.Now().Date()
or not?Also i'm resolving conflicts of PR #174 now, which involves calendar events. And the change to
time.Now().Date()
ensure if someone has events during the New Year's holiday, they will see them in the widget.Happy New Year 🎉🎉🥳
The text was updated successfully, but these errors were encountered: