omribz156 commented on code in PR #1701:
URL: https://github.com/apache/daffodil-vscode/pull/1701#discussion_r3254299807
##########
doc/Wiki.md:
##########
@@ -372,6 +392,8 @@ From left to right, the icons indicate the following
functions: Continue, Step O
* The Restart button will stop the current execution and begin again from the
beginning.
* The Stop button will immediately terminate and abort all processing.
+When the Data Editor is open during a debug session, it tracks the parser
location in the input data. As the debugger pauses on entry, steps through the
schema, or stops at breakpoints, the Data Editor highlights the corresponding
byte position so the schema, infoset, and input data can be compared together.
Review Comment:
Added this sentence in the launch section. It now says the Data Editor uses
the debug launch target file and does not prompt for a separate file selection
during a DFDL debug session.
##########
doc/Wiki.md:
##########
@@ -314,10 +322,20 @@ This default configuration will prompt the user to select
the DFDL Schema and da
"type": "file",
"path": "${workspaceFolder}/infoset.xml"
},
- "debugServer": 4711
+ "debugServer": 4711,
+ "openDataEditor": true,
+ "dataEditor": {
+ "port": 9000,
+ "logging": {
+ "file": "",
+ "level": "info"
+ }
+ }
}
```
+Set `openDataEditor` to `true` to open the Data Editor when the debug session
starts. The `dataEditor` settings configure the Ωedit server port and Data
Editor logging. Leave `logging.file` empty to use the default OS app-data/XDG
log location, or set it to a specific log file path. The launch config wizard
also exposes these settings as **Open Data Editor**, **omega-edit Port**, **Log
File**, and **Log Level**.
Review Comment:
Added the accepted Ωedit server log-level values, and verified them against
the current `@omega-edit/server` repository before updating the docs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
