microsoft / microsoft/vscode-edge-devtools

Allow Framework Ignore List -> Custom Exclusion Rules

Open
#1,480 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement tracked
Dominant language
TypeScript
Stars
827
Forks
358
Avg merge
20h 32m
Merged PRs (30d)
10

Description

Is your feature request related to a problem? Please describe.

I'm frustrated by not being able to see the correct line number when using a custom console logger.

Describe the solution you'd like:
Edge currently has the ability to setup Framework Ignore Lists with custom exclusion rules. Please make that developer setting available in the DevTools. If I add my custom logger to the framework ignore list, I will then be able to see the 'proper' line numbers.

Describe alternatives you've considered:
The alternative is to not to use vscode but to debug in the browser which respects the framework ignore list setting.

Additional context:
image

image

Because this function is defined in a separate file, with blackbox off you get a message like this:

[Scoped] blah blah blah - extras.ts:26

but with blackbox on you get

[Scoped] blah blah blah - test.ts:4

and clicking on test.ts will take you to the right file.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the VS Code DevTools extension exposes debugger settings and how Edge Framework Ignore Lists and custom exclusion rules are represented. Check the custom console logger scenario described in the issue, including the extras.ts and test.ts examples. Done means the DevTools setting accepts custom framework exclusions and produces the expected test.ts source location.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.