datetime format bestfit does not process a single configuration #190
Comments
|
The solution is to add some hard-wire in |
|
Hmmm yeah it can be a hard code point like you said.. |
|
Yeah. I took a look at the code. The calendar data is there, it's just that the possible configurations that the polyfill generates don't include single options. |
|
@juandopazo yes, we can included that as part of the data as well, that's the other part of the story. |
|
You can include the day and the month won't format either. Month can't use long for some reason. I'm trying to debug it. |
|
@gabriel-miranda yes, this is for any format that should use a single element in the formatter. |
|
solve by 20f322d please, verify if this solves all your problems ;) |
|
@caridy Thanks for the tip I ended up parsing the relative date myself and using intl-relativeformat to support the languages. Maybe in the next months I will look up again for this. Ty anyway |
Because CLDR skeletons always contain more than one configuration, or a fixed configuration for single entries, we end up missing the opportunity to provide the best result in
BestFitFormatMatcher.More examples about these are here from @mkohlmyr:
/cc @juandopazo @watilde
The text was updated successfully, but these errors were encountered: