TypeScript

809 readers

1 users here now

founded 1 year ago

MODERATORS

snowe@programming.dev

thomas@lemmy.douwes.co.uk

Ategon@programming.dev

So, are enums ok or not? (lemmy.ml)

submitted 11 months ago by lorty@lemmy.ml to c/typescript@programming.dev

12 comments fedilink hide all child comments

I have googled this and even got to the second page, and there does not seem to be any kind of consensus.

As far as I can tell, it's a bad idea because it creates code you don't see and accepts inputs that you wouldn't want. And yet, many people seem to like them more than, say, const unions due to being easier to refactor in bulk.

So what gives? Is this a case of IT people having very strong opinions on stuff that doesn't matter? Or is there a technical reason for or against it?

you are viewing a single comment's thread
view the rest of the comments

[–] spartanatreyu@programming.dev 9 points 11 months ago (3 children)

Basically, you can use them if you want to, but every single case where you would use them would be better served with a union type.

[–] pm_me_your_quackers@lemmy.world 4 points 11 months ago

To add, turning everything into an enum can make the code nearly unreadable and hard to work with. This isn't Rust, and there's no performance gain for using enums over string unions.

[–] LeafOnTheWind@lemmy.world 2 points 11 months ago

Or by an enum class.

[–] fidodo@lemmy.world 2 points 7 months ago

Another good option is const objects, it's a recommended alternative in the official docs. https://www.typescriptlang.org/docs/handbook/enums.html#objects-vs-enums