Namespaces are not handled

[JesperSporronRocker]

I have translations that are namespaced, i.e.

const { t } = useTranslation(["shared", "thisFeature"]);
const errorTitle = t("shared:error.defaultTitle");
const pageTitle = t("thisFeature:title");

However i18n-unused does not account for these namespaces, and is showing me that:*

• shared:error.defaultTitle is missing a translation (when running display-missed).
• error.defaultTitle is unused (when running display-unused).

I found an ugly fix where display-unused ignores all files that were posted in display-missed, but I can't use that with remove-unused (unless I update the config json). Adding an option to natively support this would be nice :)

[mxmvshnvsk]

Hi, I see your point. I'll look docs about this option and make update at next week. Thx for interest.

[adriandmitroca]

I believe the same situation applies to key prefixes, such as:

const { t } = useTranslation("users", { keyPrefix: "index" })

[medihack]

Unfortunately, I have the same problem of missing namespace support. And as namespaces can be configured in so many ways (even when generating the i18next instance itself), I guess this problem can't be solved perfectly. My suggestion would be to introduce a setting to be more lax. So if a key is not found in any of the locale files, then it is reported as missed. At least this is a hint then that there is something wrong. How about a PR? ;-)

[mxmvshnvsk]

@medihack I'm always for new PR's to the repository =)

[boredland]

Hi, I see your point. I'll look docs about this option and make update at next week. Thx for interest.

Hi there! Did you ever have a chance to look into it?

[mxmvshnvsk]

@boredland I hope, that yeah. But without date, maybe this weekends.

[lurenzsgp]

Hi there! I'm also interested in that issue. Do we have any advancement?