microsoft / microsoft/vscode-powerquery-sdk
Option to turn off raw row dump in output window
Open
@ptyx507x is already working on this.
Since Sep 22, 2022.
enhancement
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
VSCode's Output window contains a JSON (or JSON-like) serialization of all rows produced by the evaluated query. If that query returns a lot of rows, the output window contains a very large quantity of JSON.
Is there an option to reduce the verbosity of what is output so that rows aren't rendered here (instead are just displayed in the PQTest result pane)?
Might be nice so that Output is easier to scroll through.
Example Output
[5:34:29 PM] [Info] RunTestBattery result [
{
"ActivityId": "36489f42-6381-4393-991e-ca6a311c3fa1",
"DataSourceAnalysis": [
{
"Kind": "DataSource",
"FunctionName": "BenTest.Contents",
"DataSource": {
"kind": "BenTest",
"path": "BenTest"
},
"DataSourceReference": {
"protocol": "x-datasource",
"address": {
"kind": "BenTest",
"path": "BenTest"
},
"authentication": null,
"query": null
},
"ModuleName": null,
"ModuleVersion": null
}
],
"Details": "// Use this file to write queries to test your data connector\r\nlet\r\n result = BenTest.Contents()\r\nin\r\n result\r\n",
"EndTime": "2022-09-22T21:34:28.9025178+00:00",
"Method": "PQTest.RunTest",
"Name": "BenTest.query.pq",
"StartTime": "2022-09-22T21:34:27.7307854+00:00",
"Output": [
{
"A": 1
},
{
"A": 2
},
{
"A": 3
},
{
"A": 4
},
{
"A": 5
},
{
"A": 6
},
{
"A": 7
},
{
"A": 8
},
{
"A": 9
},
{
"A": 10
},
{
"A": 11
},
{
"A": 12
},
{
"A": 13
},
{
"A": 14
},
{
"A": 15
},
{
"A": 16
},
{
"A": 17
},
{
"A": 18
},
{
"A": 19
},
{
"A": 20
},
{
"A": 21
},
{
"A": 22
},
{
"A": 23
},
{
"A": 24
},
{
"A": 25
},
{
"A": 26
},
{
"A": 27
},
{
"A": 28
},
{
"A": 29
},
{
"A": 30
},
{
"A": 31
},
{
"A": 32
},
{
"A": 33
},
{
"A": 34
},
{
"A": 35
},
{
"A": 36
},
{
"A": 37
},
{
"A": 38
},
{
"A": 39
},
{
"A": 40
},
{
"A": 41
},
{
"A": 42
},
{
"A": 43
},
{
"A": 44
},
{
"A": 45
},
{
"A": 46
},
{
"A": 47
},
{
"A": 48
},
{
"A": 49
},
{
"A": 50
},
{
"A": 51
},
{
"A": 52
},
{
"A": 53
},
{
"A": 54
},
{
"A": 55
},
{
"A": 56
},
{
"A": 57
},
{
"A": 58
},
{
"A": 59
},
{
"A": 60
},
{
"A": 61
},
{
"A": 62
},
{
"A": 63
},
{
"A": 64
},
{
"A": 65
},
{
"A": 66
},
{
"A": 67
},
{
"A": 68
},
{
"A": 69
},
{
"A": 70
},
{
"A": 71
},
{
"A": 72
},
{
"A": 73
},
{
"A": 74
},
{
"A": 75
},
{
"A": 76
},
{
"A": 77
},
{
"A": 78
},
{
"A": 79
},
{
"A": 80
},
{
"A": 81
},
{
"A": 82
},
{
"A": 83
},
{
"A": 84
},
{
"A": 85
},
{
"A": 86
},
{
"A": 87
},
{
"A": 88
},
{
"A": 89
},
{
"A": 90
},
{
"A": 91
},
{
"A": 92
},
{
"A": 93
},
{
"A": 94
},
{
"A": 95
},
{
"A": 96
},
{
"A": 97
},
{
"A": 98
},
{
"A": 99
},
{
"A": 100
},
<< truncated to make this issue description shorter >>
],
"RowCount": 1000,
"Status": "Passed",
"TraceFileLocation": null,
"Type": "PQTest.Expression"
}
]
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.
Assessment
This issue has not been assessed yet.