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
I like the idea of this gem and would like to know if the translation cache is invalidated across the multi threads?
For example: Translation for key hello is world
Web worker A and B are holding the cache as { en: { hello: 'world' } }
A translation update request is sent to Web worker A and updated translation for hello to be zworld, I18n.backend.reload! is called and Worker A will refetch the translations and now has the cache as { en: { hello: 'zworld' } }
Does calling I18n.backend.reload! in Worker A also invalidate caches in Worker B?
The text was updated successfully, but these errors were encountered:
I don't think that the caching functionality was implemented with the multi-thread support in mind as it keeps the cache in a class variable under the hood.
I like the idea of this gem and would like to know if the translation cache is invalidated across the multi threads?
For example: Translation for key
hello
isworld
{ en: { hello: 'world' } }
hello
to bezworld
,I18n.backend.reload!
is called and Worker A will refetch the translations and now has the cache as{ en: { hello: 'zworld' } }
Does calling
I18n.backend.reload!
in Worker A also invalidate caches in Worker B?The text was updated successfully, but these errors were encountered: