fix: Keep enum prefix if would be numeric without

[paulmand3l]

Addresses #1222

Currently, if we try to generate typescript with the option removeEnumPrefix enabled and encounter and enum like:

enum Option {
  OPTION_1 = 0;
  OPTION_2 = 1;
}

We strip the enum name prefix and generate invalid typescript:

enum Option {
  1,
  2,
}

This changes this behavior to strip the enum prefix only if all resulting values are valid, advisable typescript. E.g.

enum Option {
  OPTION_1 = 0;
  OPTION_FOO = 1;
}

Becomes

enum Option {
  OPTION_1,
  OPTION_FOO,
}

This will treat as numeric:

• Any combination of pure numbers (e.g. OPTION_001010362)
• Any string with a number first (e.g. OPTION_1A)
• Infinity (e.g. OPTION_INFINITY) - note that this results in a technically valid typescript enum but seems like it will cause problems elsewhere.

[stephenh]

Looks great @paulmand3l , thank you!

[stephenh]

🎉 This issue has been resolved in version 2.8.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v2.8.2

Your semantic-release bot 📦🚀