> In the launch.json, changing the debug level to INFO didn't reduce the
huge
> debug output to the terminal.
This doesn't happen for me; the INFO and DEBUG levels are respected. Can
you share your launch.json configuration?
The relevant section from my launch.json looks like:
...
> Even if you choose output type JSON, the output infoset file is named
> infoset.xml. Should be infoset.json.
This is unfortunate, but the expected current behavior, as the
"infosetOutput.path"
parameter sets the filename of the output, but the separate "infosetFormat"
parameter sets the format
The VOTE to release Apache Daffodil VS Code Extension 1.3.1-rc1 is now
closed.
The vote fails with:
1 binding -1
1 binding +1
The VOTE thread:
https://lists.apache.org/thread/9tnjjg3l9hltv7owq2mh7sbwqmbj3634
The vote breakdown is:
+1 Mike Beckerle (binding)
-1 Robert Strickland (binding)
Hi Mike, those sound like bugs that do need to be addressed: debug levels,
json output, etc. I'll look into them to reproduce and handle issues, etc.
.. Adam
On Tue, Aug 29, 2023 at 7:59 AM Mike Beckerle wrote:
> My vote +1 (However, I see already there is a binding -1, so oh well)
>
> I want
My vote +1 (However, I see already there is a binding -1, so oh well)
I want to try some even harder schemas, but already this is more robust and
usable than 1.3.0 because it makes the error outputs more visible.
A few notes:
I like the Debug Console tab. The error messages that mention files,
