unused messages lint rule

[samuelstroschein]

Context

Over time messages became stale and are not used in source code anymore. No mechanism exists at the moment that "lints" unused messages that can safely be deleted. The result is an evergrowing amount of messages that translators are supposed to translate even though some or many messages aren't used.

Proposal

Introduce an "unused message" lint rule.

The lint rule parses the source code and searches for message references (similar/identical to the ide extensions message reference matchers)

Requirements

#2126

[samuelstroschein]

We are hesitant to implement this lint rule before caching of lint rules does not exist. Linting source code is expensive.

[buhodev]

The cost of linting the source code on every app boot-up is likely too expensive and also cancels out lix's lazy cloning that we are implementing at the moment.

Why does it need to run on every app boot-up? I usually run linting before committing

[samuelstroschein]

Good remark. I edited my comment to reflect that linting source code is too expensive not to be cached, irrelevant when the linting happens. I am mainly thinking about browser-based inlang apps like fink that need to display such lints too. A performance restricted env like the browser (that Fink runs in) could easily take minutes to fetch, parse & lint source code

[PeerRich]

awesome, would use at cal.com!

[samuelstroschein]

discussion moved to opral/inlang-sdk#6 (comment)