3 ms·
It looks like this tool applies translations at runtime via an API call. While that probably makes integrations easy for people who are mostly adding site funct
by danpalmer 5y ago
It looks like this tool applies translations at runtime via an API call. While that probably makes integrations easy for people who are mostly adding site functionality with things like Google Tag Manager, that strikes me as a poor design decision for anyone with any more control over their site.
- FlorianRappl 5y agoNot sure I get that comment. I think the API first design is good. It let's you decouple the translations from your application. It's then up to you too either do that on the server, on the client, or at build time. All three are easily possible. If you'd start with a static file then the decoupling and automation tasks will be much more difficult to achieve.
- LikeAnElephant 5y agoIt's almost universally bad practice to reference your TMS at runtime. There are always exceptions in G11N, but typically the best route is to either dump your translations into a property file or cache the translations somehow (in memory or in a DB, etc)
- jancizmar 5y agoIf you use Tolgee, you should be using translations fetched from REST API in production. So you don't reference your TMS. See: https://tolgee.io/docs/web/get_started/preparing_for_production https://tolgee.io/docs/web/get_started/preparing_for_product... Or: https://tolgee.io/docs/web/using_with_react/react_preparing_for_production https://tolgee.io/docs/web/using_with_react/react_preparing_...