Suggestion: Define a type for translations

[FabienDehopre]

I'm submitting a ... (check one with "x")

[ ] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[x] feature request

Current behavior
N/A

Expected/desired behavior
Declare (and export) a type for translation.
Instead of having Observable<any>, you can declare a type type Translation = { [key: string]: string | Translation }; and use Observable<Translation>

The type any is too vague and if I understand correctly the translation is an object where all properties are either a string or another type with string property or object (recursively).

[ocombe]

yes, it's a good idea and easy to do

[FabienDehopre]

If I have the time this weekend, I would probably do it and make a pull request by the beginning of next week.

[ocombe]

That'd be nice !

[Ghostbird]

This has been done already hasn't it?

core/projects/ngx-translate/src/lib/translate.service.ts

Lines 19 to 26 in ee77f16

	export type Translation =
	string |
	Translation[] |
	TranslationObject |
	// required to prevent error "Type instantiation is excessively deep and possibly infinite."
	// eslint-disable-next-line @typescript-eslint/no-explicit-any
	any