godot: Exported enum - inspector selection breaks when enum is updated to contain additional values

Godot version

3.4.stable

System information

Windows 7 64 bit

Issue description

Creating enums with auto-assigned integer values ends up as a bad experience when exporting them for editing in the inspector, and you need to later update them. I could have 100s of instances of an object I made but I need to add a new enum value, and this ends up breaking all of my object instances because the actual assigned values of the enums changed.

If I’m using this syntax, that means I don’t want to be concerned with the actual value of the enum, I only care that the enum name matches before the interpreter comes in to replace with an integer value.

enum SOME_ENUM {
    APPLE,
    PEAR,
    PEACH
}

But since the inspector seems to care about the integer value, not the enum name, you can end up with a mismatch of state if you add new values to the enum.

Steps to reproduce

enum SOME_ENUM {
    APPLE,
    PEAR,
    PEACH
}

export(SOME_ENUM) var enum_selection

In the inspector, select PEACH for “Enum Selection”.

Update SOME_ENUM to contain a value that comes before PEACH, such as:

enum SOME_ENUM {
    APPLE,
    GRAPE,
    PEAR,
    PEACH
}

Now “Enum Selection” will say “PEAR” instead of “PEACH”.

I’m assuming this is because Godot stores the integer value for the enum, since the integer values are auto assigned in this case, the values increment.

Minimal reproduction project

No response