We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm submitting a bug report
Please tell us about your environment:
Operating System: any
Node Version: 16.14.2
Browser: all
Language: TypeScript 4.2
Current behavior: The current prototype of i18.tr() has this prototype:
i18.tr()
tr<TResult extends string | object | Array<string | object> | undefined = string>(key: string | string[], options?: TOptions<object>): TResult;
It should instead have:
tr<TResult extends string | object | Array<string | object> | undefined = string>(key: string | string[], options?: TOptions): TResult;
where TOptions = TOptions<StringMap> by default so that one can use overloads such as:
TOptions = TOptions<StringMap>
this.i18n.tr(`key`, { some_interpolation_field: "some interpolated value", })
Expected/desired behavior:
What is the expected behavior? That one can call i18n.tr() with an interpolation map.
What is the motivation / use case for changing the behavior?
The text was updated successfully, but these errors were encountered:
Change options type for I18N.tr()
8dd2c4c
This fixes aurelia#352.
46a8339
Successfully merging a pull request may close this issue.
I'm submitting a bug report
4.0.3
Please tell us about your environment:
Operating System:
any
Node Version:
16.14.2
8.7.0
webpack 5
Browser:
all
Language:
TypeScript 4.2
Current behavior:
The current prototype of
i18.tr()
has this prototype:It should instead have:
where
TOptions = TOptions<StringMap>
by default so that one can use overloads such as:Expected/desired behavior:
What is the expected behavior?
That one can call i18n.tr() with an interpolation map.
What is the motivation / use case for changing the behavior?
The text was updated successfully, but these errors were encountered: