-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use new logger throughout code base #12
Comments
Radeonmann
added a commit
that referenced
this issue
Oct 12, 2021
Radeonmann
added a commit
that referenced
this issue
Jan 15, 2022
All existing console log were replaced. Existing functionality without log will be adjusted on change of architecture (#5) |
Radeonmann
added a commit
that referenced
this issue
Jan 25, 2022
Before, the whol environment was in one file with local variables... The new structure has classes and static classes which each represent a single environment component. This makes the code more flexible for new features and additions to single components. At the same time some components now offer more flexibility for changes in file namings and diretcory structures. The extension logger was used in all new components #12 The stray logger entry on startup is also gone now #28.
Most places now use the new logging system, so the issue will be closed. Other missing logging / overlogging will be handled in separate issues when problems arise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is a lot of code which fails without any log entry. Also at some places
console.log
was used for debugging. Other places usevscode.window.showXxxMessage
. All existing code should be scanned and log entries should be done properly.The new log API from #7 should be used everywhere.
The text was updated successfully, but these errors were encountered: