-
Notifications
You must be signed in to change notification settings - Fork 518
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(logging): leverage vscode OutputChannel, drop watch/cleanup #4688
Problem: - We start a logfile watcher on startup, which adds (1) unnecessary latency and complexity, and (2) uses node fs watcher (unreliable, not web-compatible) instead of vscode watcher. - vscode OutputChannel has gained capabilities such that we no longer need to manage logfiles: - "Open Output in Editor" - Log syntax highlighting - Set log level (TODO: we aren't currently leveraging this) Solution: - Only log to OutputChannel. Don't log to a file unless "aws.dev.logfile" (developer-mode setting) is set. - Update "View Logs" commands to show the "AWS Toolkit Logs" OutputChannel instead of the logfile (unless "aws.dev.logfile" is set). - Remove all logfile watch/cleanup code.
- Loading branch information
Showing
4 changed files
with
15 additions
and
235 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.