Skip to content

Conversation

nikitok
Copy link

@nikitok nikitok commented Dec 11, 2024

Added an optional caching mechanism to avoid translating the same keys multiple times.
The cache key is generated using the getKey function, which creates a unique identifier for each translation based on the source string, source language and target language

@ParvinEyvazov
Copy link
Member

Hi @nikitok, Thank you so much for your great contribution!

I will merge it soon after proper testing! Also can you please take a look at the conflicts?

Thanks.

@nikitok
Copy link
Author

nikitok commented Dec 17, 2024

Done.

About mechanism: we are creating cache_FROM_TO.json files, for saving state in cache (not 1 file, because we could work in multithread mode).

@himpich
Copy link

himpich commented Aug 22, 2025

Worked very well in my tests and helped me to get around API Limit problems

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

Successfully merging this pull request may close these issues.

3 participants