Skip to content

Variable not found error (in launch.json) should not be catastrophic #1555

@lrbarber

Description

@lrbarber

Description

If a variable definition has been added to the launch.json file, but that variable does not exist in the schema the debugger will not start.

Steps to Reproduce

  1. Add a viarable defintion to the launch.json file:
Image
  1. Launch debugger with launch.json file
  2. See pop-up error

Expected Behavior

This should probably just generate a warning. Definitely does not need to be an error that prevents debugger from running.

Actual Behavior

Catastrophic error that aborts debugger.
Image

Environment

  • Found on Windows 11 (but probably NOT OS dependent)
  • Extension version 1.5.0 RC 1

Metadata

Metadata

Labels

bugSomething isn't workingdebuggerIssues related to the DFDL debugger capability

Type

No type

Projects

Status

In Progress

Relationships

None yet

Development

No branches or pull requests

Issue actions