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.

Sign up for GitHub

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

Jump to bottom

Extensions: show location of console log in consoles #34936

Closed
bpasero opened this issue Sep 25, 2017 · 0 comments
Closed

Extensions: show location of console log in consoles #34936

bpasero opened this issue Sep 25, 2017 · 0 comments
Assignees
@bpasero
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality on-testplan
Milestone
September 2017

Comments

@bpasero
Copy link
Member

bpasero commented Sep 25, 2017

When using console.log from an extension we loose the location where the console.log was triggered from. We should capture the location and show it:

  • in our debug console
  • in dev tools
@bpasero bpasero added extensions Issues concerning extensions feature-request Request for new features or functionality labels Sep 25, 2017
@bpasero bpasero added this to the September 2017 milestone Sep 25, 2017
@bpasero bpasero self-assigned this Sep 25, 2017
bpasero added a commit that referenced this issue Sep 25, 2017
@bpasero
show console.log from extension host top frame in dev tools (#34936)
6762612
@bpasero bpasero mentioned this issue Sep 25, 2017
Merged
@deysaikat95 deysaikat95 mentioned this issue Sep 25, 2017
Closed
@bpasero bpasero closed this as completed Sep 25, 2017
@bpasero bpasero mentioned this issue Sep 25, 2017
Closed
3 tasks
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bpasero bpasero

Labels
extensions Issues concerning extensions feature-request Request for new features or functionality on-testplan
Projects
None yet
Milestone
September 2017
Development

No branches or pull requests
1 participant
@bpasero