lynt removed all typecast type assertions about lynt

[saadq]

Hmm, will look into this. But just to clarify – lynt does not use your tslint.json. It is basically a wrapper around TSLint and it uses its own config for it. The full TSLint config that is generated is here: https://github.com/saadq/lynt/blob/master/src/tslint/config.ts

If you'd rather use your own rules with your own config, you're probably better off just sticking with TSLint.

With that said, I'm going to take a look at these rules and see what could be causing this issue. Let me know if you find anything strange in there in the mean time!

[whyboris]

I think you're correct about 'no-unnecessary-type-assertion'
I removed the line 'no-unnecessary-type-assertion': true, from node_modules/lynt/lib/tslint/config.js (manual hack) and re-ran the npm run lynt (pacagke.json command has --typescript --fix) and it no longer removed the type assertions!
Your file: https://github.com/saadq/lynt/blob/master/src/tslint/config.ts#L80

ps -- using lynt removed about 300 unused imports in our codebase ❤️ 🙌 ❤️

pps - After lynt removed the unused imports, it left behind some blank lines, resulting in errors when I was running our regular linter: it complained no-consecutive-blank-lines. Sorry to overload this issue -- please let me know if you'd like me to open a new issue with just this comment 👍

[saadq]

This rule has been removed entirely as of v0.5.0. Release notes: https://github.com/saadq/lynt/releases/tag/v0.5.0

[saadq]

Thinking it might be this

[saadq]

lynt just uses TSLint's --fix flag, so I think the issue for that would need to be opened in the TSLint repo.

[saadq]

But let me know if for some reason this only happens when you run lynt --typescript --fix and not tslint --fix.