Suggestion: Missing Translation as Info

[ChristianHovenbitzer]

Not sure if it is possible to get translation via the language and check if any are missing, but I think this could be very beneficial.

Maybe you can share some insight? @Arthurvdv

[rvanbekkum]

Yes, it's possible. I think the only annoying thing is that I don't think it's possible for the diagnostics to point to the translation file (line) that has an issue. The ReportDiagnostic method in the Dynamics.CodeAnalysis dlls don't support the same options to raise diagnostics on (specific lines of) other file types like Roslyn allows to.
Alternatively a diagnostic could even be raised on the Caption/Label/... symbol/syntax node relevant to the issue. It is possible to determine the relevant symbol based on the "XLIFF Generator" note in the .xlf files.

[ChristianHovenbitzer]

I have started doing some development and created a draft PR just to make sure people know about this before starting to implement this themselves.

As a proof of concept this works already.

#884

[pri-kise]

There is a new warning in the Latest AL Language Preview when the xliff has changed.
Have you checked this warning already?

[ChristianHovenbitzer]

That could resolve an issue I currently have no solution for. There needs to be some sort of caching for the xliff files, reading and parsing the entire file for every caption is not an option. I'll look into this rule, and how they check if the file has changed.

Thanks for the hint.