Repository navigation
Add a cmd line options to suppress warnings #6771
Description
Activity
:+!:
why?
--warn x,y,zpulls all the "even stricter" flags under a single flag. Otherwise we'll end up with a million optional strictness flags that will drown out the other flags in documentation.looking at
--noFallthroughCasesInSwitchtells you what it does., but--suppressWarning 7029is meaningless.
The other issue here is diluting the value proposition. the main value of typescript is to catch type errors. the tooling quality depends on some of these errors being addressed by the user. if we muffle some of these errors, the whole experience would degrade. On the other hand, what we provide is a set of known knobs to switch off certain groups of errors, that we have deemed as safe to ignore.
I do not think there is anything wrong with being prescriptive here. For documentation, we could split the help into main, and extended to make sure we are not drowning common flags in the--suppres*ones- locked and limited conversation to collaborators
on Jun 19, 2018
Instead of adding a Boolean argument for each warning we want to suppress implement a more generic method to suppress, the warnings.
e.g instead of the
--noFallthroughCasesInSwitchjust suppress warning7029