From time to time, I get TSLint errors "block is empty". This happens e.g. when I pass a no-op callback to a function:
doSomething(() => {});
From what I read, JSLint apparently does the same, but I didn't verify that.
I find these usages completely valid, so I tried to find a reason why empty blocks are considered bad at all. But the only thing I'm able to find (e.g. in this answer) are instructions to add a return; to avoid the error. This is not what I want to do in every empty callback.
Why does TSLint report above empty block as problem? Is there any reason why I shouldn't disable the check?
Why does TSLint report above empty block as problem
To prevent mistakes. Perhaps the function was forgotten to be filled out. Recommend () => undefined as a noop.
If you want to disable it simply add "no-empty": false, to your tslint.json (globally disable) or disable it inline using a /* tslint:disable:no-empty */ comment.