Open ChapelR opened 4 years ago
If/when I do this, it probably won't be separate files, as that would prevent me from being able to detect macros and the like.
It would take a folder as input. But it's gonna be a bit of work
I'd appreciate support for Twee files as well, especially if that means file name + line number could be logged with each error. That would make finding the problem in the source much easier.
I don't really expect this to happen at this point. I haven't been actively working on this- if this happens somewhere it is more likely to happen in the vs-code extension "Twee 3 Language Tools"
Being able to check arbitrary text and Twee files would make this tool useful as part of a general build process when using a CLI compiler.