Skip to content
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

feat(logging): use OutputChannel log level #4859

Merged
merged 2 commits into from
Apr 28, 2024
Merged

Conversation

justinmk3
Copy link
Contributor

@justinmk3 justinmk3 commented Apr 27, 2024

Problem

  • aws.logLevel setting is unnecessary, because vscode now lets users control the log level by visiting the "AWS Toolkit Logs" output channel.
  • aws.logLevel setting may cause Q to show a Cannot register 'aws.logLevel' error.

Solution

Use the AWS Toolkit Logs" output channel log-level as the source of truth.

image

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@justinmk3 justinmk3 requested review from a team as code owners April 27, 2024 19:37
@justinmk3 justinmk3 changed the title Standalone feat(logging): use OutputChannel log level Apr 27, 2024
@justinmk3 justinmk3 marked this pull request as draft April 27, 2024 19:42
@justinmk3 justinmk3 force-pushed the standalone branch 2 times, most recently from 8f7e5e8 to 10c2209 Compare April 27, 2024 19:58
@justinmk3

This comment was marked as resolved.

@justinmk3 justinmk3 marked this pull request as ready for review April 28, 2024 17:39
@justinmk3 justinmk3 force-pushed the standalone branch 2 times, most recently from 8da7a00 to a3f9510 Compare April 28, 2024 18:21
Problem:
Q extension may show error message:

    [amazonwebservices.amazon-q-vscode]: Cannot register 'aws.logLevel'. This property is already registered.

Solution:
- Remove the `aws.logLevel` setting from both Toolkit and Q.
- Let the OutputChannel drive the loglevel.
  - For very old vscode (older than 1.74), default to "debug" log-level.
    microsoft/vscode@2cd8ea2
@justinmk3 justinmk3 merged commit 4decdf6 into feature/standalone Apr 28, 2024
14 checks passed
@justinmk3 justinmk3 deleted the standalone branch April 28, 2024 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant