TypeScript support

[AnnaTomanek]

The project I'm trying to lint with Vale is using TypeScript. The source files have a .ts extension and the comment markers are the same as in JavaScript. I've been trying to configure Vale to treat TypeScript files as JavaScript files with the following entry in my .vale.ini file:

[formats]
ts = js

but this doesn't seem to work - the output is always "✔ 0 errors, 0 warnings and 0 suggestions in N files."
However, when I change the source file extension from .ts to .js, Vale is able to read the files and lint them.

Is there anything else I should do to lint TypeScript files with Vale?
Could TypeScript support be added to the supported code formats?

[jdkato]

The docs were a bit outdated on this (now updated); Vale actually has built-in support for TypeScript (.ts, .tsx) files.

So, I'm not sure what's going on here. Could you share the rest of your .vale.ini?

[AnnaTomanek]

Thanks, Joseph, here it is - it's pretty basic as we're just starting to implement it using the available packages, with no customizations yet:

StylesPath = "scripts/vale/styles"

MinAlertLevel = suggestion

Vocab = Docs

Packages = Microsoft, proselint, write-good, Readability

[*]
BasedOnStyles = Vale, Microsoft, proselint, write-good, Readability

[formats]
ts = js

I'm trying to run it for the CKEditor 5 project - .md files are linted fine, but for our .ts files such as these: https://github.com/ckeditor/ckeditor5/tree/master/packages/ckeditor5-core/src Vale just reports ✔ 0 errors, 0 warnings and 0 suggestions in 13 files.

If the extension is changed from .ts to .js, Vale reports some issues in the code comments of the very same files.

[jdkato]

Can you try removing the format assignment

[formats]
ts = js

entirely?

[AnnaTomanek]

Looks like it works after removing the format assignment and updating Vale to the latest version. Thanks a lot for your help as well as for the excellent tool - we're really excited to implement it!

[jdkato]

Just for the record, although setting ts = js was unnecessary in this case, it still should have worked.

This will be fixed in the next release.