datepicker: shows date using provided LOCALE_ID but parses date using default US locale (or a combination of them)
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
#### Bug, feature request, or proposal:
Bug. I don't think it is working like that on purpose.
#### What is the expected behavior?
Date picker uses provided en-GB LOCALE_ID for parsing typed in date - 27/10/2018 input manually by typing is valid
#### What is the current behavior?
Typed date is parsed using US locale - 27/10/2018 input manually is invalid, 12/01/2018 is December, not January.
#### What are the steps to reproduce?
https://stackblitz.com/edit/angular-datepicker-locale?file=main.ts
1. Select 27/10/2018 using date picker.
2. Modify the date by editing the input to 26/10/2018
3. Observe invalid input
#### What is the use-case or motivation for changing an existing behavior?
Make material datepicker great again! But seriously: it seems like if a culture is provided it should affect both parsing and formatting aspects of dealing with dates and not format it into a date which is considered invalid when updated by typing.
#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
As in demo: Angular 7.1.0 Material 7.1.0. It fails validation on chrome if day (month?) is over 12, but on IE 11 is more curious as it modifies the year, I am fairly sure the swap issue causes it to work incorrectly on any browser.
#### Is there anything else we should know?
I think it may have been an issue with parsing the text date from text - it seems like it would parse using US culture ignoring provided locale.
Beitragsleitfaden
Rechercherichtung
Beginne mit dem verlinkten StackBlitz und seiner main.ts, indem du das Verhalten des en-GB datepicker reproduzierst, indem du ein Datum auswählst und anschließend bearbeitest. Verfolge, wie der datepicker eingegebene Werte formatiert und parst, und überprüfe anschließend, dass Datumsangaben wie 27/10/2018 konsistent mit dem bereitgestellten Locale akzeptiert werden und dass die bestehende Reproduktion nicht mehr bei der Validierung fehlschlägt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- frontend, internationalization
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 42/100