microsoft / microsoft/vscode-powerquery-sdk
Output split between "Output" and "Terminal" panes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Preflight Checklist
- I have installed the latest version of Power Query SDK.
- I have checked existing resources, including the common issues and the release notes.
- I have searched for similar issues.
Power Query SDK
0.1.7
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
No response
VSCode version
No response
PQSdkTool Path
No response
Bug Description
When VSCode builds an extension then evaluates the current file, the command line statements run + results produced are spliit between VSCode's "Output" and "Terminal" panes.
Steps to Reproduce
Edit extension file so that the SDK rebuilds it, then run "Evaluate current file."
Actual Experience
VSCode "Terminal" pane:
Executing task: c:\Users\ben\.vscode\extensions\powerquery.vscode-powerquery-sdk-0.1.7-win32-x64\.nuget\Microsoft.PowerQuery.SdkTools.2.110.3\tools\MakePQX.exe compile
{
"TargetMezRootPath": "C:\\Users\\ben\\Desktop\\TestConnector\\BenTest\\bin\\AnyCPU\\Debug\\BenTest.mez",
"RelativePathsOfContent": [... {output truncated for brevity}
* Terminal will be reused by tasks, press any key to close it.
VSCode "Output" pane:
[5:28:40 PM] [Info] [Task found] c:\Users\ben\.vscode\extensions\powerquery.vscode-powerquery-sdk-0.1.7-win32-x64\.nuget\Microsoft.PowerQuery.SdkTools.2.110.3\tools\PQTest.exe run-test
--extension "c:\Users\ben\Desktop\TestConnector\BenTest\bin\AnyCPU\Debug\BenTest.mez"
--queryFile "c:\Users\ben\Desktop\TestConnector\BenTest\BenTest.query.pq"
--prettyPrint
[5:28:42 PM] [Info] RunTestBattery result [
{
"ActivityId": "5594a7b4-6688-4e53-9682-18fbf197ca5a",
{output truncated for brevity}
Expected Experience
Both sets of output to appear in the same pane (i.e. either both in "Terminal" or both in "Output"). That way, the user can see all commands that were used in one place.
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the command flow for "Evaluate current file" and how its build and test output are sent to VS Code's Output and Terminal panes. Reproduce the reported Windows workflow, then verify that the compile commands and evaluation results appear together in one pane.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100