-
-
Notifications
You must be signed in to change notification settings - Fork 7k
[Bug Report][3.7.4] Wrong number week with locale-provider "fr" #20724
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@MatthewAry :Can you tell me if this issue can be definded like a bug? |
|
I will mark this a bug and bring this to the attention to other members of the team because I don't know what commitment has been made to sticking to the ISO 8601 spec. I do note that the VDatePicker uses date-io and the native date object in it's logic. I also note that there is explicit support for internationalization by mounting custom date adapters to the root createVuetify method. |
Thx @MatthewAry ! |
We have the same issue. This means that all weeks for 2025 currently is off by one week in the date-picker. It seems to be a bug in the getWeek() implementation as described here #20490 vuetify. Rather than vuetify using its own implementation the adapters instance week implementation should be used i.e. dayjs('2024-12-30').week() which returns the correct localized week. However, the date-io adapter interface does not seem to have support for week number which is mentioned here #644 date-io |
Environment
Vuetify Version: 3.7.4
Vue Version: 3.5.13
Browsers: Firefox 128.0, Google Chrome
OS: Windows 10
Steps to reproduce
When I use the v-locale-provider with "fr" around the v-date-picker, the weekNumber for the first week of 2025, the date-picker write the week 53.
The weekNumber will be week 01 for the December 30, 2024 to January 5, 2025.
Expected Behavior
Display the week 01 for the December 30, 2024 to January 5, 2025. ISO 8601 right
Actual Behavior
Display the weekNumber 53 for the December 30, 2024 to January 5, 2025.
Reproduction Link
Original Playground
Playground for v3.8.0
The text was updated successfully, but these errors were encountered: