We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Test for #14728 Complexity: 4
Should probably cover both path types:
We previously supported having the skipFiles attribute in the launch config. Now, you can also right click on a stack frame to skip or un-skip it.
Using node2, check these things:
If you aren't sure what code to test, I usually write something like this:
a.ts:
import * as b from './b'; function f() { console.log('f'); } b.callback(f);
b.ts
export function callback(cb) { cb(); }
Then you can easily verify that when b.ts is skipped, you can do a step-in to step directly from b.callback(f) to f.
b.callback(f)
f
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Test for #14728
Complexity: 4
Should probably cover both path types:
We previously supported having the skipFiles attribute in the launch config. Now, you can also right click on a stack frame to skip or un-skip it.
Using node2, check these things:
If you aren't sure what code to test, I usually write something like this:
a.ts:
b.ts
Then you can easily verify that when b.ts is skipped, you can do a step-in to step directly from
b.callback(f)
tof
.The text was updated successfully, but these errors were encountered: