You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently various libraries and applications that use terminal.writeVerboseLine and similar have no way of knowing if the information will ever make it to a file or the user. If the ITerminal could be inspected to determine the minimum severity of messages that will be visible, the effort of constructing data that is only visible with verbose logging could potentially be skipped where it will not be retained.
Since ultimately the authority on message severity comes from the underlying ITerminalProvider implementations/instances, this information would need to be surfaced there and aggregated inside of ITerminal.
As a specific example, heft-lint-plugin performs a bunch of work to compute ESLint rule timings, but that information is only exposed when running with --verbose:
Summary
Currently various libraries and applications that use
terminal.writeVerboseLine
and similar have no way of knowing if the information will ever make it to a file or the user. If theITerminal
could be inspected to determine the minimum severity of messages that will be visible, the effort of constructing data that is only visible with verbose logging could potentially be skipped where it will not be retained.Since ultimately the authority on message severity comes from the underlying
ITerminalProvider
implementations/instances, this information would need to be surfaced there and aggregated inside ofITerminal
.As a specific example,
heft-lint-plugin
performs a bunch of work to compute ESLint rule timings, but that information is only exposed when running with--verbose
:rushstack/heft-plugins/heft-lint-plugin/src/Eslint.ts
Lines 184 to 199 in 7aa7b9f
The text was updated successfully, but these errors were encountered: