This project is read-only.


0.9.1.x regression: intellisense breaks when errors encountered


update for reopen (20130827)
if you mean this is fixed in, it is not.
if you mean that it's already been fixed in the yet-to-be-released next version, could you guys expidite this? it's really really annoying to have to reload my solution every time i make a change to one of my core-library .ts files

original issue:
simple repro using v0.9.1.1

1) create a new project, put in these two files

export module A
    //STEP 1: to cause this bug, comment this next line, build, uncomment, build, and then try to reference A from b.ts
    export class AClass
        constructor(public x: string, private y: number, z: any) { }
import A = require("a");

export module B
    export class BClass
        constructor(public x: string, private y: number, z: any) { }

//STEP 2: once you cause the bug, you can not type the following and get intellisence
var a = new A.A.AClass(null, null, null);
2) follow "step1" in a.ts
3) follow "step2" in b.ts
Closed Nov 19, 2013 at 9:37 PM by RyanCavanaugh
Thanks for reporting this! The issue has been fixed and can be tried out in the upcoming 0.9.5 release. We also have a beta available ( if you'd like to try it out.


novaleaf wrote Aug 22, 2013 at 2:23 AM

for clarity, when i say in "step1" "comment the next line" i mean comment out the " export class AClass" line, so as to cause a compile error.

danquirk wrote Aug 22, 2013 at 11:46 PM

This appears to be fixed in the latest bits

** Closed by danquirk 08/22/2013 3:46PM

RyanCavanaugh wrote Aug 27, 2013 at 10:26 PM

I'm able to reproduce this

novaleaf wrote Sep 17, 2013 at 2:16 AM

fyi, i tried out the VS 2013 RC, and I don't see the issue.

but with VS 2012, I literally can not make any code changes in a .ts file without intelisence breaking for all it's dependents.

novaleaf wrote Sep 20, 2013 at 5:28 AM

please disregard my previous comment: the bug still occurs in VS 2013 RC, just less often.