Circular dependencies problem about love-typescript-definitions HOT 3 CLOSED

Hello again!

Yep, this is a TypescriptToLua issue. Some more considerations need to be made with the module resolution.

Two workarounds I can think of:

• Use interfaces
• Define the two classes in a single file

At least until this issue is resolved. If this can be resolved, classes will be able to know each other in any order but using each other may be a different story.

Here's how you'd do it with interfaces:

// global.d.ts
// IFoo is now known globally without import
interface IFoo {
    a: number;
    b: number;
}
// IBar is now known globally without import
interface IBar {}

// foo.ts
export class Foo implements IFoo {
    bar: IBar;  // IBar is known
    a: number;  // These MUST be defined according to the interface spec
    b: number;
}

/// bar.ts
export class Bar implements IBar {
    foo: IFoo;  // IFoo is known
}

from love-typescript-definitions.

This has been fixed now! It is coming up on the next TypeScriptToLua release

from love-typescript-definitions.

This is now possible in TypeScriptToLua 0.21.0!

from love-typescript-definitions.