Trying out the preview version of `.d.ts` generation, ran into issues / unsupported things very fast...

# javascript

[diesieben07]

Trying out the preview version of .d.ts generation, ran into issues / unsupported things very fast (can't even export enums 😕). Off to youtrack I go...

[turansky]

Kotlin enum doesn’t have direct analog in TypeScript, isn’t it?

[diesieben07]

It doesn't, but I'd expect it to generate a matching declaration file... Not just... nothing.

[diesieben07]

And yes, we need inline enums (or something like that) badly, for JS interop.

[turansky]

Do you use serialization for enums?

[diesieben07]

No, why?

[turansky]

In my cases union type can be generated according serialization annotation

[diesieben07]

Can you elaborate? Is this about kotlinx.serialization?

[turansky]

@Serializable
enum class Mode {
    @SerialName("normal") NORMAL
    @SerialName("undefined") UNDEFINED
}

[turansky]

In d.ts I want to see

type Mode = 'normal' | 'undefined'

[diesieben07]

How does that help with .d.ts generation and calling Kotlin from Typescript?

[turansky]

I will send you related ticket if you have same case

[diesieben07]

My use case is writing Common code in Kotlin and using it in Backend and also from Frontend written in typescript

[diesieben07]

I am not sure how serialization can help there, but I am all ears

[turansky]

How it works now in your cases?

[diesieben07]

It doesn't work at all yet, the current backend is written in PHP and code is duplicated. This is an experiment for a potential future rewrite of the backend in Kotlin

[turansky]

If TypeScript is only load data (no transformation), then you can avoid redundant enum declaring

[diesieben07]

What do you mean?