scholarsmate opened a new issue, #1725: URL: https://github.com/apache/daffodil-vscode/issues/1725
## Goal Make the Apache Daffodil VS Code extension use the standalone OmegaEdit Data Editor VS Code extension instead of carrying and starting an embedded Data Editor implementation. ## Plan - Declare the OmegaEdit Data Editor extension as a VS Code extension dependency. - Keep Daffodil's existing `extension.data.edit` command, but delegate file opening to the OmegaEdit extension API. - Convert Daffodil debugger `daffodil.data` events into external current-byte highlights in OmegaEdit. - Remove the embedded Svelte Data Editor, OmegaEdit server/client lifecycle code, and related launch configuration settings. - Update tests so Daffodil validates the integration contract with a small fixture extension instead of starting the old embedded editor stack. - Update documentation to describe the external Data Editor dependency and Daffodil's responsibility for open/highlight integration. ## Validation Criteria - TypeScript build, lint, VS Code integration tests, and license checks pass. - Opening a Daffodil data file still works through the existing command. - Debugger data-position events highlight and reveal the current byte in the OmegaEdit Data Editor. -- 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]
