arosien commented on issue #269: URL: https://github.com/apache/daffodil-vscode/issues/269#issuecomment-1405464359
> The text in the block looks good, though I'd like to find some way to trim a prefix of that big long file path based on say, the current project's root dir? I can extract the particular fields, and possibly massage them, from the diagnostic data structure rather than this impl which uses `toString`. > If that block is a pop up that's the wrong idea. It's the hover text. 👍 > It should be a thing like the call-stack on the left, where you can open it and see the contents as things get added. It should have two sub-categories within it for processing errors and for validation errors. > > Think of it this way. In some cases, every parsed element will generate one of these validation errors, and the user may simply want to ignore that for hours/days/weeks while worrying about bigger problems like parse errors. So they can't be anything that makes too much noise or requires dismissal via any UI gesture. It's in the "Parse" subtree under the "Variables" pane, so it's expandable/contractable. I'll separate the errors from warnings as separate trees. -- 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]
