Should I use `enum` or an `interface` with inline ...

# javascript

[hfhbd]

Should I use enum or an interface with inline functions and unsafeCast to reduce binary size?

[turansky]

What is your use case?

[hfhbd]

I want to provide a typed API, so I want to limit the usage using enums.

public enum class Color(private val value: String) {
    Primary("primary"),
    Secondary("secondary"),
    Success("success"),
    Info("info"),
    Warning("warning"),
    Danger("danger"),
    Light("light"),
    Dark("dark")
}

Alternative:

public interface Color {
    public companion object Theme {
        public inline val Primary: Color get() = Color("primary")
        public inline val Secondary: Color get() = Color("secondary")
        public inline val Success: Color get() = Color("success")
        public inline val Danger: Color get() = Color("danger")
        public inline val Warning: Color get() = Color("warning")
        public inline val Info: Color get() = Color("info")
        public inline val Light: Color get() = Color("light")
        public inline val Dark: Color get() = Color("dark")
    }
}

public inline fun Color.background(): Color = Color("bg-${unsafeCast<String>()}")
public inline fun Color(value: String): Color = value.unsafeCast<Color>()

the second approach was provided by Oleksandr: https://github.com/JetBrains/compose-jb/pull/859#issuecomment-875737202
but does this really result in smaller code? It's definition is uncommon and not so handy.

[turansky]

https://github.com/JetBrains/kotlin-wrappers/blob/master/kotlin-react-dom/src/main/generated/react/dom/html/AutoComplete.kt

[turansky]

Lightweight CSS types you can find here:
https://github.com/JetBrains/kotlin-wrappers/tree/master/kotlin-csstype

cc @Oleksandr Karpovich [JB]

[hfhbd]

Sorry, could you please explain it?

[turansky]

Which example? AutoComplete ?

[hfhbd]

Everything 😄
For classes already defined in JS standard, like `AutoComplete, you use external enum, which sounds nice.
What about non defined things?

[hfhbd]

And many packages in kotlin wrapper includes some docs from react. Are all packages without react in its name safe to use without react? I dont want to include react only for useful! types 🙂

[turansky]

csstype - common library

[turansky]

AutoComplete and all other enums, which emulate string unions are also common

[turansky]

csstype can be used as dependency of Compose

[turansky]

“Unions” from react packages must be copied/adopted

[turansky]

FYI - https://github.com/turansky/seskar#unions

[hfhbd]

I created a ticket to integrate some wrapper in compose web :)
https://github.com/JetBrains/compose-jb/issues/1433

[ankushg]

Is it possible to expose something like an external enum class as a Typescript enum instead of a Union type?

[turansky]

Example required