feat: use logger pattern for translator

[lem-onade]

Removed old translators (one in dgt-utils and one in dgt-components)

Created new translator with factory

[lem-onade]

Not sure why that test fails, I've tried removing the mocked fetch in tests/setup.ts, but error stays. Seems componentsjs is suddenly looking for npm modules when it shouldn't

[BelgianNoise]

@lem-onade For some reason test coverage dropped in the dgt-components package.
I am just going to lower it because it doesn't make any sense, good with you?

[lem-onade]

@lem-onade For some reason test coverage dropped in the dgt-components package. I am just going to lower it because it doesn't make any sense, good with you?

because there's 1 failing test in dgt-components

[lem-onade]

A thought: creating a new MemoryTranslator will always try to fetch the translation file, can we perhaps fetch and store this once in the factory?

or should I not have copied the getTranslatorFor, which returns a translator for a specific class? Perhaps a global translator (with getTranslator) is enough?

[woutermont]

Yes, an (additional) factory that already keeps the files is a good option. Maybe the translator need to be adapted then to take an optional translation file as dependency

[lem-onade]

Yes, an (additional) factory that already keeps the files is a good option. Maybe the translator need to be adapted then to take an optional translation file as dependency

Will implement this, also do you that getTranslatorFor and the labels on translators are not needed like they are with the loggers?

[woutermont]

Labels probably not, since nothing is printed (though it would not hurt to leave them in). Still, a getTranslatorFor is usefull to distinguish translators based on different parts of the app (might someday come in handy).

[lem-onade]

Labels probably not, since nothing is printed (though it would not hurt to leave them in). Still, a getTranslatorFor is usefull to distinguish translators based on different parts of the app (might someday come in handy).

I refactored getTranslatorFor to return a translator for a specific language, rather than a label, wdyt?