There's a CLI architecture issue that intersects with this issue. We do not have a centralized logger. This makes respecting verbosity requirements ad-hoc, on the implementor. E.g. there are lots of adhoc options.verbose, isVerbose, logVerboseExitCode(), etc.
We should ideally instead have something like logger.brief(), logger.warning(), logger.error(), and use eslint to ban console.log, console.error, etc. To enforce verbosity is consistent and causing less flow-control complexity.
Seems like a nice to have, but we'll have to make sure it's something that makes sense for both @react-native-windows/cli, and react-native-windows-init
There's a CLI architecture issue that intersects with this issue. We do not have a centralized logger. This makes respecting verbosity requirements ad-hoc, on the implementor. E.g. there are lots of adhoc
options.verbose
,isVerbose
,logVerboseExitCode()
, etc.We should ideally instead have something like
logger.brief()
,logger.warning()
,logger.error()
, and use eslint to banconsole.log
,console.error
, etc. To enforce verbosity is consistent and causing less flow-control complexity.Originally posted by @NickGerleman in https://github.com/microsoft/react-native-windows/issues/9515#issuecomment-1034677274