Skip to content

i18n: consider turning on type-checking for translations #61818

@ahrjarrett

Description

@ahrjarrett

Hello!

First I want to say thank you to the maintainers here are freeCodeCamp for making education more accessible 🙇

The i18next team is considering adding a new API that would allow i18next to support type-checking for arbitrarily-sized translation sets.

Here's the issue, if you're curious: i18next/i18next#2322

If you'd like to see this issue get merged, please give it a 👍 ! That will help signal to the maintainers that the ecosystem would find this change useful :)

To make the transition smoother for larger teams (like freeCodeCamp!), we've implemented a codemod.

If you're open to it, I'd love to help be a steward of this transition, and would be happy to run the codemod and get things started.

In my experience, running the codemod tends to uncover mistakes in key selection, especially in projects that weren't able to take advantage of type-checking previously.

If I do open a PR, I'd be happy to either make the necessary changes to complete the migration, or hand it off to someone else on the team. The latter option is probably ideal, since I might not have the necessary context to make the right decision in every case.

Thanks for reading! LMK if I can answer any questions about the change, or if you have any feedback about the direction we'd like to take the i18next DX!

Metadata

Metadata

Assignees

No one assigned

    Labels

    scope: tools/scriptsScripts for supporting dev work, generating config and build artifacts, etc.status: PR in worksWork in Progress (WIP) Issues.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions