Skip to content
New issue

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

Usage with transloco prefix #1267

Open
CorentinGROSDEMOUGE opened this issue Jan 10, 2025 · 0 comments
Open

Usage with transloco prefix #1267

CorentinGROSDEMOUGE opened this issue Jan 10, 2025 · 0 comments

Comments

@CorentinGROSDEMOUGE
Copy link

CorentinGROSDEMOUGE commented Jan 10, 2025

Is your feature related to a specific framework or general for this extension
Transloco

Is your feature request related to a problem? Please describe.
I use the prefix property with the transloco pipe.

i18-ally does not seems to be able to peek the keys then.

<ng-container *transloco="let t; prefix: 'deep.path.to.my.keys'">
    <span class="title">{{ title() }}</span>
    <span class="update-date">{{ t('update-date', {"update-date": updateDate() | translocoDate}) }}</span>
</ng-container>

I have the key translated in a .json file because when i don't use prefix, the extension works perfectly (thanks for that btw)

Describe the solution you'd like
Someway to read the prefix and prefix the parsed key with its content
So, in the previous example, instead of reading update-date it will read correctly deep.path.to.my.keys.update-date

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant