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
First off, thank you so much for this awesome project! I've been experimenting with it and really appreciate how cool and useful it is. 🙌
While using it in a TypeScript project with strict mode enabled, I encountered an issue. Specifically, whenever I use $i18n() inside a script tag or a .ts file, I get the following error: Unsafe call of an 'any' typed value.
After some digging, I noticed that the TranslationFunction is currently defined as:
I was wondering if there are specific cases where the return type might need to be something other than a string. If not, do you think it would be possible to adjust the return type to avoid these TypeScript errors? I understand there may be more context I’m missing, so any guidance or clarification would be greatly appreciated!
Thanks again for the great work on this project. Looking forward to hearing your thoughts!
The text was updated successfully, but these errors were encountered:
👋 Hey there,
First off, thank you so much for this awesome project! I've been experimenting with it and really appreciate how cool and useful it is. 🙌
While using it in a TypeScript project with strict mode enabled, I encountered an issue. Specifically, whenever I use
$i18n()
inside ascript
tag or a.ts
file, I get the following error:Unsafe call of an 'any' typed value.
After some digging, I noticed that the
TranslationFunction
is currently defined as:I was wondering if there are specific cases where the return type might need to be something other than a string. If not, do you think it would be possible to adjust the return type to avoid these TypeScript errors? I understand there may be more context I’m missing, so any guidance or clarification would be greatly appreciated!
Thanks again for the great work on this project. Looking forward to hearing your thoughts!
The text was updated successfully, but these errors were encountered: