-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-17913] fix: zh-TW registerLocaleData missing extra error #13210
base: main
Are you sure you want to change the base?
Conversation
Thank you for your contribution! We've added this to our internal tracking system for review. Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process. |
New Issues (9)Checkmarx found the following issues in this Pull Request
Fixed Issues (2)Great job! The following issues were fixed in this Pull Request
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #13210 +/- ##
==========================================
- Coverage 35.48% 35.48% -0.01%
==========================================
Files 3007 3007
Lines 90899 90904 +5
Branches 16908 16908
==========================================
+ Hits 32260 32261 +1
- Misses 56137 56141 +4
Partials 2502 2502 ☔ View full report in Codecov by Sentry. |
Modify naming method
🎟️ Tracking
#12933
#6821
#5220
📔 Objective
Fix zh-TW time format requires extra Day Periods.
I looked at angular/angular#54114 where they talked about Unable to find zh-Hant-TW, but bitwarden uses zh-Hant so it doesn't affect the usage.
what we encountered is the locale DatePipe error.
The default time format of CLDR zh-Hant is Bh uses Day Periods.
Angular places Day Periods in the extra folder.
Use translation, which may not be grammatically correct🙇
📸 Screenshots
desktop
web
browser
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes