mbeckerle opened a new issue, #649:
URL: https://github.com/apache/daffodil-vscode/issues/649
If I modify my schema and make any mistake, then I get a blocking dialog
showing the SDEs.
This is basically intolerable, because you must dismiss it, and thereby lose
the information you need from it, in order to look back at the schema to try to
fix it.
Back when the vscode extension was only a debugger this may have been more
tolerable, because it was assumed that one would author the schema elsewhere.
But now with the intellisense features coming along, one wants to author/edit
the schema in the vscode extension also. So it needs to support editing the
schema, getting SDEs, stepping through the SDEs so you can fix them. Try again,
etc. until it is runnable. And then run in the debugger.
The bare minimum fix would be to output the SDEs to a terminal window, or
other persisting window that one can scroll back and forth in. Anything
non-blocking really.
You must be able to move through the SDEs as you move the editor to fix the
schema.
I tested this on 1.3.0-RC2 of the vscode extension
--
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]
