I often end up with files with invalid code that appear to be valid, or conversely files that appear to contain errors but in fact do not.
The best scenario to reproduce this is to have 2 separate files, one which depends on the other.
E.g. B.ts has a reference to A.ts -> changes to A.ts do not force a re-compilation of B.ts which could now be invalid due to interface changes.
I will have to type random garbage in B.ts, and then delete it for a file to be marked as dirty and then re-compiled (sometimes even this doesn't work).
I often end up with files with invalid code that appear to be valid, or conversely files that appear to contain errors but in fact do not.
The best scenario to reproduce this is to have 2 separate files, one which depends on the other.
E.g. B.ts has a reference to A.ts -> changes to A.ts do not force a re-compilation of B.ts which could now be invalid due to interface changes.
I will have to type random garbage in B.ts, and then delete it for a file to be marked as dirty and then re-compiled (sometimes even this doesn't work).