Improve `check` performance on large code bases about gts HOT 7 CLOSED

Doesn't something like this work?

npm run check -- src/foo.ts src/bar.ts ...

from gts.

Not really. I want to run npm run check after npm test, just like we set up with init.

from gts.

In my experiments it was around 24 seconds, not minutes :p. Here's a profile that shows something interesting:

Why so much idle?

I think it would be better to fix this idle time issue before diving into keeping track of changed files between runs.

from gts.

I am guilty of exaggerating. When you add up the many times I run tests, it hits minutes quick though 😂

from gts.

Okay, so the 'idle' time is actually clang format. It seems that checking format takes longer than running lint, even though clang-format is implemented in C++.

from gts.

Is it a design choice to suppress the details of tslint and/or clang-format errors?

clang-format reported errors... run `gts fix` to address.

I feel like a default "show all the errors" behavior would be preferable with an option to suppress?

from gts.

We have switched to prettier via #259 (on the next branch). If this is still an issue, it probably belongs on the prettier repo.

@usergenic the details of the formatting errors are now shown in detail.

from gts.