duboisfordwork opened a new issue, #1362: URL: https://github.com/apache/daffodil-vscode/issues/1362
1. Obtain a pre-existing, known good TDML file. Below is a screenshot of the TDML I used in this reproduction <img width="1650" height="307" alt="Image" src="https://github.com/user-attachments/assets/e95b70e3-d807-41f3-a9f0-8e6e1fd656f0"; /> 2. Use a launch config similar to the following. Note that `tdmlConfig.action=execute` and `openDataEditor=true` are required to observe this bug. ```json { "version": "0.2.0", "configurations": [ { "request": "launch", "type": "dfdl", "name": "Wizard Config", "schema": { "path": "${command:AskForSchemaName}", "rootName": null, "rootNamespace": null }, "data": "${command:AskForDataName}", "debugServer": 4711, "infosetFormat": "xml", "infosetOutput": { "type": "file", "path": "${workspaceFolder}/target/infoset.xml" }, "tdmlConfig": { "action": "execute" }, "trace": true, "useExistingServer": false, "openDataEditor": true, "openInfosetView": false, "openInfosetDiffView": false, "daffodilDebugClasspath": [], "dataEditor": { "port": 9000, "logging": { "file": "${workspaceFolder}/dataEditor-${omegaEditPort}.log", "level": "info" } }, "dfdlDebugger": { "logging": { "file": "${workspaceFolder}/daffodil-debugger.log", "level": "INFO" } } } ] } ``` 3. Select the named config and press the green arrow from VS Code. <img width="606" height="114" alt="Image" src="https://github.com/user-attachments/assets/a021c47f-8fe3-498b-a79f-c9f6f1eead2c"; /> 4. Select the TDML from step 1 and the desired test case. 5. After the infoset is generated, observe that the data editor prompts the user to point to the datafile despite it already being defined in the TDML case <img width="1079" height="152" alt="Image" src="https://github.com/user-attachments/assets/eb629145-6491-4a96-a651-fab74a233ea5"; /> -- 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]
