Perhaps a factor in this feature being implemented (or not) is that @George feels it wouldn't be useful or needed.
I don't doubt there is some good advice here, but I don't understand the point about nested conditionals. I expect one of the main reasons that people want else-if statements etc. is to avoid the need to use nested conditions - which are indeed difficult to manage.
It's also been suggested there's less need for this feature because we now have the library feature.
I would suggest there's even more need for switch/else-if functionality, to increase the usefulness of the library feature. A particularly useful library file might be able to take a long list of parameters from different API files; what better way to handle these than with switch or else-if statements. The alternative at the moment would be to use some very clumsy code.
I was looking at a large chunk of code I maintain/develop (in a different environment). It contains over 1300 Else-If statements. I'm pretty confident these help to make the code better and easier to maintain, rather than the opposite. I sometimes consider the possibility of recreating this in Wappler; the thought would be a lot more appealing if this basic programming feature were available.
Anyway, I live in hope...