search

michaelangeloio / does-it-throw

lsp server for finding ES statements that throw!
MIT License
84 stars 0 forks source link

Add CLI tool version #59

Open PalmDevs opened 10 months ago

PalmDevs commented 10 months ago

Hi there, this project is really neat for catching errors beforehand. But it seems that it's currently limited to specific code editors.

I use Git hooks to lint my commits, so an addition of a CLI tool would be great. This will also open a door for unsupported tools.

michaelangeloio commented 9 months ago

@PalmDevs hey!

would like to get more input on what you image the CLI would look like? Would it show all the errors via stdout? Would it give a summary? Want to get your thoughts

PalmDevs commented 9 months ago

@PalmDevs hey!

would like to get more input on what you image the CLI would look like? Would it show all the errors via stdout? Would it give a summary? Want to get your thoughts

Hello! I think having the CLI only showing errors would be nice.

I can imagine doing something like npx does-it-throw and it'd just check for you, then it prints out errors (in stderr and exits with a non-zero code) if an error is found, in a similar format to when you get type errors using the TypeScript compiler (tsc).

A summary would be a nice feature too, but I'd personally put that under a sub-command/argument, since you usually don't want anything printing out when everything is successful.