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?
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.
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.
Or by an enum class.
Use enums when you need enums. Don’t use them when you don’t need them. What’s the issue?
At work, when I was helping with some frontend stuff, we used object literals.
const DIRECTIONS = { UP: "UP", DOWN: "DOWN" } as const; type DIRECTIONS = typeof DIRECTIONS[keyof typeof DIRECTIONS];Taken from option 2 in this blog post. https://maxheiber.medium.com/alternatives-to-typescript-enums-50e4c16600b1`___`
This is, in my opinion, the absolute best way to do it
Yes
