You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the variable reference, we may be able to do something like:
{
"id": "filename",
"type": "promptString",
"description": "(Optional) Enter a part of the test file name (e.g. 'foo' will run 'foo.spec.ts', 'notfoo.spec.ts', 'test.foo.spec.ts', etc.)",
"default": "${fileBasename}"
}
Which will use the currently opened file as the default. Looking at the predefined variables There are ways to be smarter about it:
${relativeFile} will contain the following: <workspaceFolder>/sdk/<serviceDirectory>/<packageDirectory>/test/public/node/myTest.spec.ts (for example, if we have that file open)
There are command extensions that can be used to split and manipulate that string
We can write a launch config that takes no parameters and smartly splits out the relative path and the filename and passes those in. I suggest we do that separately and I'll create an issue to look into it 👍 It's a great idea IMO
The text was updated successfully, but these errors were encountered:
maorleger
added
Client
This issue points to a problem in the data-plane of the library.
and removed
Client
This issue points to a problem in the data-plane of the library.
labels
Nov 14, 2024
Looking at the variable reference, we may be able to do something like:
Which will use the currently opened file as the default. Looking at the predefined variables There are ways to be smarter about it:
<workspaceFolder>/sdk/<serviceDirectory>/<packageDirectory>/test/public/node/myTest.spec.ts
(for example, if we have that file open)We can write a launch config that takes no parameters and smartly splits out the relative path and the filename and passes those in. I suggest we do that separately and I'll create an issue to look into it 👍 It's a great idea IMO
The text was updated successfully, but these errors were encountered: