You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which Transloco package(s) are the source of the bug?
Don't know / other
Is this a regression?
No
Current behavior
The TranslocoGlobalConfig interface is missing the "keysManager.sort" property. As a result, the following TypeScript configuration file does not work without additional modifications, because TypeScript reports that the "keysManager.sort" property does not exist on the TranslocoGlobalConfig interface.
The text was updated successfully, but these errors were encountered:
xDivisionByZerox
changed the title
Bug(scope): TranslocoGlobalConfig interface is missing "sort" property
Bug(transloco-utils): TranslocoGlobalConfig interface is missing "sort" property
Jan 9, 2025
Is there an existing issue for this?
Which Transloco package(s) are the source of the bug?
Don't know / other
Is this a regression?
No
Current behavior
The
TranslocoGlobalConfig
interface is missing the "keysManager.sort" property. As a result, the following TypeScript configuration file does not work without additional modifications, because TypeScript reports that the "keysManager.sort" property does not exist on the TranslocoGlobalConfig interface.If you remove the types and run a TKM command, it functions as expected (sorting the keys). The issue lies solely with the interface.
Expected behavior
I can define the "keysManager.sort" property on the configuration object while keeping the type without additional modifications to the type itself.
Please provide a link to a minimal reproduction of the bug, if you won't provide a link the issue won't be handled.
https://stackblitz.com/edit/stackblitz-starters-4pegy8i9?file=transloco.config.ts&view=editor
Transloco Config
No response
Please provide the environment you discovered this bug in
Browser
No response
Additional context
No response
I would like to make a pull request for this bug
Yes 🚀
The text was updated successfully, but these errors were encountered: