JeremyYao commented on PR #1521: URL: https://github.com/apache/daffodil-vscode/pull/1521#issuecomment-3522901114
### Testing methodology 1. Set data path to empty <img width="558" height="153" alt="image" src="https://github.com/user-attachments/assets/11b40e65-730f-4239-aefb-df8324c23caf"; /> 2. Verify empty data path or undefined data path exists exists <img width="674" height="577" alt="image" src="https://github.com/user-attachments/assets/08ca72e7-dcfe-4f2c-848f-65804756ee09"; /> It doesn't seem to be possible to set it to `undefined`. Only empty string if you set the text field to be blank 3. Deleted my launch.json file and recreated a new one via config wizard 4. Can confirm that the input data file path is empty <img width="518" height="736" alt="image" src="https://github.com/user-attachments/assets/6af5324e-8a3e-42ac-a6b6-167503e4d988"; /> 5. launch.json schema populated and ran fine ```JSON { "version": "0.2.0", "configurations": [ { "request": "launch", "type": "dfdl", "name": "Wizard Config", "schema": { "path": "${command:AskForSchemaName}", "rootName": null, "rootNamespace": null }, "data": "", "debugServer": 4711, "infosetFormat": "xml", "infosetOutput": { "type": "file", "path": "${workspaceFolder}/target/infoset.xml" }, "tdmlConfig": { "action": "generate", "name": "Default Test Case" }, "trace": true, "stopOnEntry": true, "useExistingServer": false, "openDataEditor": false, "openInfosetView": false, "openInfosetDiffView": false, "daffodilDebugClasspath": [], "dataEditor": { "port": 9000, "logging": { "file": "${workspaceFolder}/dataEditor-${omegaEditPort}.log", "level": "info" } }, "dfdlDebugger": { "daffodilVersion": "3.11.0", "timeout": "10s", "logging": { "file": "${workspaceFolder}/daffodil-debugger.log", "level": "INFO" } } } ] } ``` ### Feedback I noticed that the settings.json property uses `"data"`. This seems to go against other naming conventions in my settings.json file as well as against https://code.visualstudio.com/docs/configure/settings#_settings-json-file. There may also be an issue where some other extension may use `"data"` and its value too given that it doesn't have a prefix to its name. Extension's global settings usually has it So the pattern is: **`<your-extension-prefix>.<settingName>`** * `<your-extension-prefix>` is typically your extension’s identifier, e.g., the name you used in `package.json` (often publisher+name) or a namespace you choose. * `<settingName>` is a meaningful name for that specific setting. See https://chatgpt.com/share/6914b97d-1a70-800b-a08e-2bef5ee9952e -- 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]
