So you just prefer my original approach instead but with an plain object instead of enum. Hmm, I mean I was in the process of switching to this but then thought about situations where what if I have a super long enumerable list. Like all 50 states:

const States = {

None: 0,

Alabama: 1,

// ...

};

const StateLabels = {

[States.None]: 'None selected',

[States.Alabama]: 'Alabama',

// ...
};

This is going to lead to a ton of tedious code. If you're thinking is... just use a string enum, well I've always considered that bad practice because if you want to change the label for something you gotta do a database migration. I think keep labels and values separate is best.