Are there plans to return external enums in the future? This looks ugly: ```sealed external class D...

# javascript

[altavir]

Are there plans to return external enums in the future? This looks ugly:

sealed external class DropEffects {
    @JsName("copy")
    object Copy : DropEffects

    @JsName("move")
    object Move : DropEffects

    @JsName("link")
    object Link : DropEffects

    @JsName("none")
    object None : DropEffects
}

[turansky]

In most cases such unions are open in fact

[turansky]

As result - const enums (new feature) will solve only half of problem

[altavir]

Idea suggests to use data objects. But obviously, you can't do that for external subclasses.

[turansky]

In described example objects aren't required, val is fine

[altavir]

You mean simple constants?

[turansky]

Yes, like here

[turansky]

sealed external interface Align {
    companion object {
        val TOP: Align
        val LEFT: Align
        val BOTTOM: Align
        val RIGHT: Align
    }
}

[altavir]

I see

[turansky]

We use objects only in case, when separate types are really required

[turansky]

One more example of constant

[turansky]

Which bonuses do you expect from enums in your case? Short declaration only?

[altavir]

yes

[turansky]

DropEffects in your example - string union emulation?

[altavir]

Yes. In this particular case, I think string constants will do. But it is an import from TS.