Closes #1554
Description
When you open the launch wizard, and create a new config and save, when you go back to the original config the rootname and rootnamespace will be " " instead of null. This leads to a Namespace error when you run the extension
This issue will be fixed with my MR to add wizard support for tunables. But in the case that a user added "null" or "" to the launch.json, the debugger would fail to run. This can be a seperate issue if the scope is going to be larger.
Steps to Reproduce
[
-
Go to launch wizard
-
Click on new config
-
Name the config and save
-
Go back to launch wizard and select the new config
- In my branch there were scenarios where I ran into "" as well as "null"
]
Expected Behavior
We expect null value. Not null string, or " ". DFDL is expecting a null value specifically
Actual Behavior
It seems we are getting empty " " and in some scenarios "null"
Additional Notes and Screenshots (optional)
Environment
[
]
Closes #1554
Description
When you open the launch wizard, and create a new config and save, when you go back to the original config the rootname and rootnamespace will be " " instead of null. This leads to a Namespace error when you run the extension
This issue will be fixed with my MR to add wizard support for tunables. But in the case that a user added "null" or "" to the launch.json, the debugger would fail to run. This can be a seperate issue if the scope is going to be larger.
Steps to Reproduce
[
Go to launch wizard
Click on new config
Name the config and save
Go back to launch wizard and select the new config
]
Expected Behavior
We expect null value. Not null string, or " ". DFDL is expecting a null value specifically
Actual Behavior
It seems we are getting empty " " and in some scenarios "null"
Additional Notes and Screenshots (optional)
Environment
[
Operating System(s): Linux
Browser/VS Code version:
Extension version:
]