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

Add (trace) logging to help extension author trouble shoot notebook code actions #184027

Open
jrieken opened this issue Jun 1, 2023 · 0 comments
Assignees
Labels
notebook-code-actions Notebook editor code actions under-discussion Issue is under discussion for relevance, priority, approach
Milestone

Comments

@jrieken
Copy link
Member

jrieken commented Jun 1, 2023

re #183855

Consequence of #183855 (comment) and me being confused how to get this to work. It would be helpful to have some trace logging in the renderer for when/how code actions for notebooks are applied. This could prevent question/answer issues and empower extension authors

@Yoyokrazy Yoyokrazy added this to the June 2023 milestone Jun 1, 2023
@Yoyokrazy Yoyokrazy modified the milestones: June 2023, July 2023 Jun 26, 2023
@Yoyokrazy Yoyokrazy modified the milestones: July 2023, August 2023 Jul 25, 2023
@Yoyokrazy Yoyokrazy modified the milestones: August 2023, September 2023 Aug 31, 2023
@Yoyokrazy Yoyokrazy modified the milestones: September 2023, Backlog Sep 28, 2023
@Yoyokrazy Yoyokrazy added under-discussion Issue is under discussion for relevance, priority, approach notebook-code-actions Notebook editor code actions labels Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notebook-code-actions Notebook editor code actions under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

2 participants