I am looking at the generated type definitions by ...

# javascript

[andylamax]

I am looking at the generated type definitions by 1.6.20-M1. I gotta admint, @JsExport got the love it truly deserves

Kudos to the whole team for such accomplishments. A lot of my issues (infact, all I have reported recently) have been already solved

[ankushg]

Excited to try it out!

[andylamax]

Sadly, one thing makes the types definitions unusable. The generated file exposes companion objects on interfaces as a static getter. while at this moment, Typescript doesn't support static members/methods on interfaces

[hfhbd]

one thing? what about this https://youtrack.jetbrains.com/issue/KT-51205? it makes exporting and using with typescript unusable :D

[andylamax]

@hfhbd I am failing to reproduce your external class is mapped to any problem. Coz to me it works just fine

package battleground.problem

@JsExport
external interface User {
    var name: String
    var email: String
}

@JsExport
val pete: User = jso { }

Yields

export namespace battleground.problem {
    interface User {
        name: string;
        email: string;
    }
}
export namespace battleground.problem {
    const pete: battleground.problem.User;
}

[andylamax]

Also, regarding to the promises problem, I don't have the problem because I don't use promises at all. I use a multiplatform of Promise called a Later, it can be found here https://github.com/aSoft-Ltd/foundation/tree/master/foundation-runtimes/later

[hfhbd]

Use a class

[andylamax]

Use a class

This code

package battleground.problem

@JsExport
external class Promise<T>

@JsExport
val promise: Promise<Unit> = TODO()

generates the following types

export namespace battleground.problem {
    class Promise<T> {
        constructor();
    }
}
export namespace battleground.problem {
    const promise: battleground.problem.Promise<void>;
}

Are you sure you tried that on 1.6.20-M1?

However, I have noticed kotlin.js.Promise<T> is indeed exported as any // kotlin.js.Promise<T>

[andylamax]

While experimenting on this, I also noticed that

@JsExport
external class Promise<T> {
   companion object
}

Does not compile. For it to compile, you either remove the companion object, or @JsExport You can't seem to have both and make it work

[hfhbd]

Using your own Promise class does not work with typescript interoperability, because it is not mapped to js.Promise.

[andylamax]

not when you copy the type definition in kotlin.js.Promise into a file that is not inside a package. This is indeed a workaround though

[Grégory Lureau]

What's the point to use @JsExport and external on the same class? It's just for testing 1.6.20-M1 or I'm missing something?

[andylamax]

What's the point to use @JsExport and external on the same class?

If you just declare it as external the generated .d.ts won't include its definitions. @JsExport makes your external class types available in the generated .d.ts