Feature request: Eslint plugin

[Demivan]

Discussed in fluent-vue/fluent-vue#743

^{Originally posted by Demivan October 4, 2021}

Check for:

• Missing translation in the main locale
• No computed keys
• Reusing translations keys
• Invalid fluent syntax

[Ericlm]

I think it would be great to report raw text in files, like https://eslint-plugin-vue-i18n.intlify.dev/rules/no-raw-text.html 🙂

[Ericlm]

@Demivan would it be okay to make a new scaffold with https://github.com/AlbertHernandez/typescript-library-template?tab=readme-ov-file to have newest deps? I would be willing to do it if needed 🙂

[Demivan]

I'm not sure that this project is needed at all. What rules do you think would be useful?

Invalid fluent syntax is now reported by the Vite plugin. Missing translations are better handled by the translation system. no-raw-text would be a copy of Intlify one.

[Ericlm]

I was thinking about the rules that https://eslint-plugin-vue-i18n.intlify.dev can reports; but I thought it was for vue-i18n only, not for fluent. Maybe am I wrong?

[Demivan]

It was designed for vue-i18n. But I see no reason why no-raw-text, for example, would not work with fluent-vue.

We are using fluent-vue for a long time now, and I never really thought that we need eslint for it. What vue-i18n rule you find useful for your use case?

[Ericlm]

Indeed, no-raw-text should still work, but duplicate keys especially with multiple files, is quite important. And in the same way, missing keys, or dynamic ones.

But I agree on the fact that this would be nice but not essential.

[Demivan]

I'm fine with merging PRs if you want to implement the functionality :)