Closed jon9090 closed 6 days ago
@jon9090 Can you please share why would you name these two scopes with the same name?
The scope isn't overridden because Transloco has an internal cache, and by giving the same name to the scope, Transloco assumes that this is the same translation.
@jon9090 In case you missed my previous comment ☝️
Feel free to reopen.
Is there an existing issue for this?
Which Transloco package(s) are the source of the bug?
Transloco
Current behavior
I created an example using
scope
. In the example code, there are two components (foo
andbar
), each with its own translations. The app component toggles between these two components. When a component loads, it should also load its respective translations using theinline
prefix (scope).Each component has its own scope, but they written the same key. It seems that
provideTranslocoScope
doesn't override the existinginline
translations. Why is this happening?Here's the code:
You can view and modify the code on StackBlitz: StackBlitz Example