Integration with Transloco Locale

[lppedd]

What problem does this feature solve?

This is more of a question (tho not suited for StackOverflow given it requires knowing implementation details).
I see that date locale depends on Angular's "native" i18n integration, or alternatively on date-fns.

Let's say that I don't use any of them, and instead use Transloco (which is pretty much the go-to solution nowadays), how would we approach integrating with Transloco Locale (https://jsverse.gitbook.io/transloco/plugins-and-extensions/locale-l10n) for components like the Date Picker?

What does the proposed API look like?

To be decided. Transloco operates lazily instead of eagerly like Angular i18n.

[lppedd]

To better understand how it works, the central piece of code is TranslocoLocaleService, and especially TranslocoLocalService.localizeDate.

[Laffery]

I think we should not integrate with transloco directly, instead we can provide an abstract service for people who wanno integrate with any third-party library to customize the NzI18nService, WDYT @lppedd

[lppedd]

@Laffery yes that's exactly what I was thinking about. It is also a step forward in the sense the main ng-zorro-antd package doesn't have to depend on date-fns directly, but can delegate to a secondary/separate one instead.

Let's say we want to go ahead with this, what are the main pieces of code that will be impacted? I know we already have an Nzi18nService, but is it the only source of truth?

[Laffery]

Let's say we want to go ahead with this, what are the main pieces of code that will be impacted? I know we already have an Nzi18nService, but is it the only source of truth?

My search result in the codebase:

• Nzi18nService
• CommentModule
• DatePickerModule
• RangePickerModule