Remove enums from the code base

[zharinov]

Describe the proposed change(s).

This is an umbrella issue for series of small refactoring PRs

[pret-a-porter]

What is the reason to remove enums?

[zharinov]

Risks seem to be outweighting the benefits. But doing converting enums for hostType I've realized we actually need not only enumerate values, but also validate them (e.g. when set via user config). So, the problem is a bit wider then one versus another idiomatic construct.

[pret-a-porter]

Also please check, that const enum compilation result same to union type https://www.typescriptlang.org/play?#code/MYewdgzgLgBApmArgWxgFTtGBvAsAKBiJgHkw4YBeGARgBoDj0B3EKmAJgfwF8CCAZojDAoAS3AwAhgBMZACgAeALnSYodGAE9VGaAEpVSZACM4AJxyMY5uFETmwMRTADU2gNwE++ArIX0nPpe+EA

[pret-a-porter]

Cause of using classic enum in case of ProgrammingLanguage is looping through all possible values

[zharinov]

In context of Renovate, personally my biggest obstacle with enums is that we can't import type { SomeEnum } from 'somewhere'.

[zharinov]

Maybe, it's easily solvable, though

[viceice]

In context of Renovate, personally my biggest obstacle with enums is that we can't import type { SomeEnum } from 'somewhere'.

That why i don't like them too. I now always union types instead.

[renovate-release]

🎉 This issue has been resolved in version 34.29.0 🎉

The release is available on:

• GitHub release
• 34.29.0

Your semantic-release bot 📦🚀