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
#54001 enabled extensions to log their telemetry to log files but only when VS Code is started from the cli with --verbose flag. The same should be allowed to do when VS Code is started normally and the log level is changed to trace.
For this we need the log level related api to be promoted form the proposed mode to stable which is planned for the August release
The text was updated successfully, but these errors were encountered:
@jrieken I am taking a look at this item. Am I understanding correctly that only part of the logging api made it out of proposed (the log folder)? If so, I am still blocked on this item or can I determine the log level has been changed?
@sbatten There still is no API for this and even if there was we don't create a log file anymore. Instead we would want to shared the same output channel as telemetry which isn't currently possible. The proposed solution would be to create a telemetry API for this to happen, but I don't see that occurring. Closing for now as we have --telemetry as a CLI flag which contains all the extensions which we run the tooling against and which extensions can contribute to.
#54001 enabled extensions to log their telemetry to log files but only when VS Code is started from the cli with
--verbose
flag. The same should be allowed to do when VS Code is started normally and the log level is changed totrace
.For this we need the log level related api to be promoted form the proposed mode to stable which is planned for the August release
The text was updated successfully, but these errors were encountered: