Declaring a different defaultNS than "translation" allows unexpected cases on t function. [Typescript]

[ImADrafter]

🐛 Bug Report

Declaring a different defaultNS than "translation" allows unexpected cases on t function.

Related issues: #1301

I think the issue might be related to this line since 'translation' is hardcored.

To Reproduce

codesandbox;

// i18nConfig

i18n.use(initReactI18next).init({
  defaultNS: "ns1",
  resources: {
  sk: {
    ns1: {
      a: "translated A"
    },
    ns2: {
      b: "translated B"
    },
    ns3: {
      c: "translated C"
    }
  }
} 
});

// App.tsx
  const { t } = useTranslation();
  ...
  <h4>{t("c")}</h4> {/* It should not compile */}

Expected behavior

When a specifing a different defaultNS than "translation", TS compilation should not allow cases that are not supported by JS implementation.

Your Environment

• i18next version: i.e. 20.2.1
• react-i18next version: 11.8.13

[pedrodurek]

Hey @ImADrafter, It's not possible to automatically infer the defaultNS from t function based on the options passed to the init function. The workaround available right now is this:

const { t } = useTranslation<'ns1'>();

Since people have been requesting the ability to override the defaultNS (without using the workaround above), I'm going to open a PR this week to accommodate that using type augmentation (the same technique we use to infer keys and return types for t function). For now, let's keep this issue opened.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.