Skip to content

Project dependents will put error squiggles on dependency project #2386

@ScottCarda-MS

Description

@ScottCarda-MS

Describe the bug

When you have multiple projects open in VS Code, an error in one place can get error squiggles from multiple projects. The squiggles from other projects won't be cleared until code form that project is touched.

To Reproduce

Steps to reproduce the behavior:

  1. Create Q# project Foo with an error in it:
operation FooOp : Unit {
   NotDefined();
}
export FooOp;
  1. Create another Q# project Bar that depends on Foo:
{
  "dependencies": {
    "Foo": {
      "path": "../Foo"
    }
  }
}
operation Main() : Unit {}
  1. Look back to the code in Foo and notice that there is an error for NotDefined() not being defined.
  2. Delete the line for NotDefined().
  3. The error for NotDefined() will persist even though it is not present in the code anymore.
  4. Touch the code in Bar.
  5. Notice the persistent error for NotDefined() will be gone.

This is happening because Bar put an error in Foo for the NotDefined() issue, even though it wasn't Bar's code.

Expected behavior

Projects should not put error squiggles in their dependency's code.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions