On a file that doesn't reference another file that defines a class, use of that class does not result in an error

[fionafung]

Sunk to Master as of 02/23/2015, 12:00pm.

I have my file cat.ts which does not reference dog.ts. dog.ts defines the class "Dog". In cat.ts, I'm trying to create a "Dog" class - I should get an error that "Dog" isn't defined (at least I used to). Now I don't get the undefined error

[steveluc]

fixed in 2badb26

[fionafung]

Hey Steve,
Sunk to tip on Master this morning and I still see that "Dog" is not squiggled. However, another unreferenced class "Bird" (which is not defined anymore, is inde3ed squiggled.

[steveluc]

The closest thing I've been able to repro is that if I bring up cat.ts alone both are squiggled. If I then bring up dog.ts, Dog is OK, but Bird is squiggled. Then if I close dog.ts, Dog does not get squiggled until I modify cat.ts once more (then both are squiggled). This happens because we are not yet sending an event to the client when project structure has changed.

I see in both your screenshots that dog.ts is up. If dog.ts references cat.ts (as in my repro), then Dog will be defined as long as dog.ts is open. dog.ts referencing cat.ts makes a virtual project with dog.ts and cat.ts. If dog.ts is closed, a new virtual project is created with only cat.ts (so the squiggle should appear), but the squiggle will not appear until you once again modify cat.ts, because we are not yet sending a project changed event back to the editor.

[steveluc]

Fiona, can you try again to repro this?

[fionafung]

Here is the behavior without a tsconfig.json file:
With just cat.ts open, Dog is squiggled in cat.ts.
With cat.ts and dog.ts opened, Dog is not squiggled in cat.ts
I believe that this is now the supported behavior.
With tsconfig.json, Dog is correctly not squiggled.