rthomas320 commented on code in PR #1331:
URL: https://github.com/apache/daffodil-vscode/pull/1331#discussion_r2245386108


##########
DEVELOPMENT.md:
##########
@@ -374,6 +375,32 @@ The local Apache Daffodilâ„¢ Extension for Visual Studio 
Code downloads and cach
     This will start the debug adapter and await a connection from the Apache 
Daffodil VS Code Extension (usually on TCP port 4711); and
 - debug your schema file, as long as it has the `useExistingServer` setting 
above.
 
+#### Debugging UI Source
+
+After starting an Extension debug window and setting up the Data Editor, open 
the Webview Developer Tools with `Ctrl + Shift + P` and type `Developer: Open 
Webview Developer Tools`. 
+
+![ui-debug1](https://github.com/user-attachments/assets/14ccd4dc-b8e1-4555-add9-b4dd106a82b9)
+
+Select the Sources tab in the tool window.
+
+![ui-debug2](https://github.com/user-attachments/assets/97e84c81-b0fd-4ac0-8488-a2c0115b0eba)
+
+In the navigation pane on the left, select the file to place breakpoints.
+
+![ui-debug3](https://github.com/user-attachments/assets/c63ba4d3-1963-4ce2-81a1-751a54b8acf7)
+
+Place breakpoints by clicking the line number.

Review Comment:
   If you set a breakpoint in Web Developer Tools, do you need to go back to 
the extension and do something to hit the breakpoint? Do you need to restart 
the extension or the Data Editor? Or is there a run button in the Web Developer 
Tools pane?



##########
DEVELOPMENT.md:
##########
@@ -374,6 +375,32 @@ The local Apache Daffodilâ„¢ Extension for Visual Studio 
Code downloads and cach
     This will start the debug adapter and await a connection from the Apache 
Daffodil VS Code Extension (usually on TCP port 4711); and
 - debug your schema file, as long as it has the `useExistingServer` setting 
above.
 
+#### Debugging UI Source
+
+After starting an Extension debug window and setting up the Data Editor, open 
the Webview Developer Tools with `Ctrl + Shift + P` and type `Developer: Open 
Webview Developer Tools`. 
+
+![ui-debug1](https://github.com/user-attachments/assets/14ccd4dc-b8e1-4555-add9-b4dd106a82b9)
+
+Select the Sources tab in the tool window.
+
+![ui-debug2](https://github.com/user-attachments/assets/97e84c81-b0fd-4ac0-8488-a2c0115b0eba)
+
+In the navigation pane on the left, select the file to place breakpoints.
+
+![ui-debug3](https://github.com/user-attachments/assets/c63ba4d3-1963-4ce2-81a1-751a54b8acf7)
+
+Place breakpoints by clicking the line number.
+
+![ui-debug4](https://github.com/user-attachments/assets/3375876f-c4e6-4df0-a383-c57dbcb7727e)
+
+You can then inspect values by either opening the Memory Inspector

Review Comment:
   The breakpoint needs to be hit before you can inspect values, correct?



-- 
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]

Reply via email to