Turn all boolean options into enums?

[lassik]

I've been thinking about this for a while. Quoting from here:

Language version may become a first class feature for Unibeautify. Prettier's Trailing Commas option has an es5 option: https://prettier.io/docs/en/options.html#trailing-commas
Whereas Unibeautify's End With Comma option is boolean (only true or false): https://unibeautify.com/docs/option-end-with-comma.html?language=javascript

Should we have boolean beautifier options at all? It seems that for many options that initially seem like an 'on' or 'off' kind of thing, people will later realize that there is a third alternative. Having everything be an enum from the start would enable us to add new alternatives more gracefully. many clang-format options seem to be specified with this in mind in.

[Glavin001]

I have been thinking the exact same thing!

A lot of the existing Unibeautify options were copied from Atom-Beautify. I definitely think they need improving, both in terms of the possible option values supported and also if they should be renamed ( #182 ).

[Glavin001]

@stevenzeck thoughts?