-
Running version 3.X of the package is working fine in Storybook etc, however when we come to write tests for our component, we get the following error:
```
Test suite failed to run
Cannot find …
-
I have translations that are namespaced, i.e.
```typescript
const { t } = useTranslation(["shared", "thisFeature"]);
const errorTitle = t("shared:error.defaultTitle");
const pageTitle = t("thisF…
-
Based on this discussion: https://github.com/openmsupply/open-msupply/pull/1252#discussion_r1120823118, please read it for context.
Main concern is that localisations are not fully type safe:
**…
-
The big goal for the next major release is to get everything out of the way that a) makes the setup harder than necessary and b) could slow down feature development for the foreseeable future.
Feat…
-
### What's not working?
After setting i18n up, I tried to translate the NotFoundPage with the hook `useTranslation()`
`useTranslation()` generated an error : "Rendered more hooks than during the p…
titib updated
2 years ago
-
## 🐛 Bug Report
In my app we use some dynamically loaded translation files where the namespace is not in `serverSideTranslations` and instead we use the `ready` flag (from `useTranslation`) to de…
-
When extraction the keys, if an extraction error happens (for example, because of a dynamic key that can't be solved like `t(myVariable)`), all the remaining valid keys in the entire file will be igno…
-
[gatsby i18n](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-i18n)
[tutorial](https://lokalise.com/blog/gatsby-i18n/)
-
### Steps to reproduce
Either pigment or next-i18next i18n library can work on a project:
https://github.com/rkurbatov/acq-test - here is example repository for NextJS v12. We managed to fix nex…
-
## To Reproduce
Name this file with .ts extension (configured with JavascriptLexer) and the keyPrefix is ignored, if you use JsxLexer instead, it's works
```typescript
export default function use…