feat: add ide-extension for i18next handling

[NilsJacobsen]

Let me know if I need to change something to merge this PR

I added the inlang IDE extension to sealos. Helps with handling translation keys and translation linting.

What did I add?

• inlang.config.js to configure where language translations are
• Would recommend adding it to the .vscode folder so other contributors can use it.

How to use it?

Extract Messages (translations)

Extract Messages (translations) via the Inlang: Extract Message code action.

Inline annotations

You can see translations directly in your code. No back-and-forth looking into the translation files themselves. (code example from sealos)

Ootb editor & CLI if needed.

[cla-assistant]

All committers have signed the CLA.

[sealos-ci-robot]

🤖 Generated by lychee action

Summary

Status	Count
🔍 Total	844
✅ Successful	322
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	521
❓ Unknown	0
🚫 Errors	0

Full action output

Full Github Actions output

[NilsJacobsen]

Hey btw sealos has 16 erros (missingMessage/ referenceMessageMissing) in the translation.

This could negatively effect the user experience.

[NilsJacobsen]

I also sow that the key Recharge Amount is often used but not in the translations. Probably an old key.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (613ce0f) 72.97% compared to head (34a9d68) 72.97%.
Report is 660 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3474   +/-   ##
=======================================
  Coverage   72.97%   72.97%           
=======================================
  Files           8        8           
  Lines         618      618           
=======================================
  Hits          451      451           
  Misses        132      132           
  Partials       35       35           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fanux]

@c121914yu inlang seems to be a good method for i18n, please follow up on this pull request.

[c121914yu]

How do I get it started?
Do I need to install other packages? or IDE extension.
Please give a complete example.

Because we are using the i18n ally plugin locally. I'm not sure if inlang can be replaced it.

[NilsJacobsen]

@c121914yu

How do I get it started?
Do I need to install other packages? or IDE extension.
Please give a complete example.

After merge, you just need to open vscode with the inlang ide-extension installed. It should automatically work.
Usage is documented here -> https://inlang.com/documentation/apps/ide-extension

Because we are using the i18n ally plugin locally. I'm not sure if inlang can be replaced it.

i18n-ally can also be used as a helper with i18n, but inlang is going for the infrastructure approach, which caught me. What does it mean:

• Comes with i18n products that are just usable ootb with the config. (ide-extension, cli, editor)
• no lock-in, for those who want to use i18n-ally it is not a problem
• inlang is being built fast, while i18n-ally is basically unmaintained by localize Reactivate i18n-ally community: Let's collaborate! lokalise/i18n-ally#896

In conclusion, inlang can replace it. Especially with the release of opral/monorepo#960 and opral/monorepo#724. But as I said there is no need to decide (no lock-in).

[c121914yu]

I have added the inlang.config.js file locally and have installed the inlang extension. But didn't seem to see much effect.
I see an sdk in the inlang documentation, do I need to install it?
Or I need to add a configuration in.vscode/settings.json?

[NilsJacobsen]

I see an sdk in the inlang documentation, do I need to install it?

The SDK is only relevant if you didn't localize yet.

Or I need to add a configuration in.vscode/settings.json?

There shouldn't be anything to change here.

You can test if the config is valid with npx @inlang/cli config validate. -> https://inlang.com/documentation/apps/inlang-cli#config-validate
If that works you should see the inline annotations. Sometimes you need to reload the window. While doing that on the bottom left corner it should say inlang extension activated. After some seconds it should show the annotations and of course, you could use the extract function.

[stale]

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

[NilsJacobsen]

inlang did a big update which requires an update on this PR.

-> Whats new

Should I change it?

[c121914yu]

inlang did a big update which requires an update on this PR.

-> Whats new

Should I change it?

Thank your PR. We will re-evaluate the i18n when we rebuild the architecture in Q4.

[stale]

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

[NilsJacobsen]

Hi @c121914yu just wanted to check-in if you talked already about i18n in Q4?
What are/were the topics you want to discuss? Do you have some pain points with it right now?

[stale]

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.