-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
cody: cody.debug.filter setting to enable debug logging #52236
Conversation
Bundle size report 📦
Look at the Statoscope report for a full comparison between the commits a371fa5 and 22abdcb or learn more. Open explanation
|
ff75f52
to
a135fb6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved into the VS Code Cody directory, because we need to define a debug
method that uses VS Code APIs
@@ -18,13 +18,17 @@ export function getRecipe(id: RecipeID): Recipe | undefined { | |||
return registeredRecipes[id] | |||
} | |||
|
|||
function nullLog(filterLabel: string, text: string, ...args: unknown[]) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not debug log anything in Cody web at this time.
a135fb6
to
fb2c773
Compare
fb2c773
to
848328c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's much needed, thanks!
Removes the
cody.debug
behavior in favor of three settings:cody.debug.enable
cody.debug.verbose
cody.debug.filter
Introduces a
debug
function that will log output to the VS Code Output channel "Cody AI by Sourcegraph", accessible in the "Output" bottom panel and then selecting "Cody AI by Sourcegraph" from the dropdown. This is intended for collecting information about client-side execution from end users reporting errors with Cody.Test plan
Only affects logging behavior