Štěpán Granát
Štěpán Granát
Yep, the post process hook could basically solve this. But it must be done in a clever way, so it's only included in dev mode. As this will basically include...
Yeah, basically I think we could have a configuration option on tolgee core to postprocess a translation after is downloaded from the platform. That should be pretty universal. And then...
Hey, could you also share the Tolgee initialization?
Hmm, that looks OK 🙁 One other thing you can debug is to check how is the tolgee cache looking after you load the data. If you add this piece,...
This probably only works by accident in `t` function, it was not intended. But as you describe it it make sense. I'll look into it.
There is a clash with tag interpolation in `T` component. All the params of T component which include a React node are transformed to a function, so it is compatible...
Hey, unfortunately this is not solvable easily. The problem comes from friction between i18next and Tolgee. As Tolgee serves as simple backend, it loads data when i18next requests them. The...
It's not about Tolgee initialization, but about i18next initialization. Because you ask i18next to load translations, which will use TolgeeBackend to load them - Tolgee starts, but then in the...
For the tag command to work, it requires a new parameter `filterKeysNot`, which will select oposite of listed keys. That way, we can find deprecated keys like this: ```sh tolgee...
Assigning @JanCizmar , let me know if you need some changes in translator