Localization labels & messages not working
See original GitHub issueHi Daniel, I’m trying to use the localization & messages like in your example / docs here, but it doesn’t seem to work: https://danielykpan.github.io/date-time-picker/#locale-formats
It will throw the same errors like in the “Localization” example on stackblitz : https://stackblitz.com/github/DanielYKPan/owl-examples/tree/date-time-picker
ERROR
Error: Unable to process animations due to the following failed trigger transitions
@transformPicker has failed due to:
- `query("@fadeInPicker")` returned zero elements. (Use `query("@fadeInPicker", { optional: true })` if you wish to allow this.)
I’m using Angular 6 and the newest version (6.0.8) of your date time picker.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Localization problems with Messages interface - Google Groups
Hello all, I have a gwt application. All my labels and messages are localized. I use Constants, ConstantsWithLookup and Messages interface. The only...
Read more >localization of label that only accepts strings not working in ... - Telerik
The problem is that label only accepts strings and throws an error, hence the localization does not work, some help would be appreciated....
Read more >Launchscreen ignoring my localizat… | Apple Developer Forums
It ignores completely my localization in Pt-Br. I have just a label on it with a loading message. I've tried both strings and...
Read more >Error messages in the Localization Framework
Error messages are displayed when the appropriate settings are not configured for the translation and workflow preferences.
Read more >10 Key Localization Mistakes, and How to Avoid Them | Phrase
You can solve this problem by leaving extra space after each label for the string to grow. However, by doing so, the labels...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The format of the class DefaultDateTimeIntl should be import { Injectable } from ‘@angular/core’; import { OwlDateTimeIntl } from ‘@danielmoncada/angular-datetime-picker’;
@Injectable() export class DefaultDateTimeIntl extends OwlDateTimeIntl { public cancelBtnLabel = ‘Cancel’; public setBtnLabel = ‘Apply Date/Time’; }
Thanks, and the example should be fixed now.
When we use a customised localization intel, we need to extends the origin class
OwlDateTimeIntl
;