shanedell commented on code in PR #929:
URL: https://github.com/apache/daffodil-vscode/pull/929#discussion_r1443565989
##########
src/launchWizard/launchWizard.js:
##########
@@ -64,7 +64,7 @@ function getConfigValues() {
'openInfosetDiffView'
).checked
const openInfosetView = document.getElementById('openInfosetView').checked
- const program = document.getElementById('program').value
+ const schema = document.getElementById('schema').value
Review Comment:
@mbeckerle Yes, so the reason for the TS and JS files is because the JS file
directly interacts with the DOM/UI of the WebView. For the scripting of
WebViews it only directly support JS and not TS, so we use JS to interact with
UI and then forward that information to the TS. We also use JS to update the UI
based on information sent back to the JS from the TS. So, overall JS is used
mostly for DOM and UI interaction and the TS does everything else but they
communicate back and forth with each other using the VSCode API. The JS version
of that API in this case has a lot less capabilities than the VSCode API in the
TS and that is why we don't use only JS for this as well.
Does that help or make it more confusing?
--
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]
