Closed
Description
TypeScript Version: 3.7.2
Visual Studio Version: VS 2019 Community (16.4)
Search Terms:
error underlining
Repro Steps
- Project A contains 'library' code in file
aaa.ts(Project has 'composite' set to true). - Project B references A and consumes a interface Foo declared in
aaa.ts - Ensure all files in B are closed.
- Open file
aaa.ts. - Add a new method to interface Foo (which would cause breakage in B).
- Rebuild B and check the output window for the expected error.
- In the output window double click on the error line to see the error.
- This will open the offending file in B.
Expected behavior:
The file in B should have the error underlined
Actual behavior:
There is no error underlining.
Other points to note:
- Restarting Visual Studio causes the error underlining to show up correctly.
- If the offending file in Project B is already open then the error underlining works correctly.
There is no way to reproduce this as the error occurs only in a very large project set up. However, we have captured language service logs according to the instructions. Please provide a contact email to send through the logs. I cannot post them here as there is potentially sensitive information.
Usual spiel on why this should be fixed urgently
We are basically operating in the dark without error underlining.