Default toggles addition

[ppo]

Is your feature request related to a problem?

No, just some suggestions to be added?

Describe the solution you'd like

Foreword

• The principle is that it's better to have many different options as it's easy cycle between them.
• Can you have different lists relative to the current editor/programming language?

Misc

• ["and", "or"], (useful in Python)
• ["null", "undefined", "NaN", "None", "nil"], (JavaScript, Python…)
• ["map", "reduce", "filter"],
• ["thead", "tbody", "tfoot"],
• ["dark", "light"],
• ["hot", "warm", "cool", "cold"],
• Log levels + success: ["success", "critical", "error", "warning", "notice", "info", "debug"], (Wikipedia)
  • Or Bootstrap: ["success", "warning", "danger", "info"],

Change these?

From	To
["x", "y"],	["x", "y", "z"],
["start", "stop"],	["start", "stop", "end", "pause"],
["left", "right"],	["left", "right", "middle", "center", "justify"],
["head", "body"],	["head", "body", "foot"],
["row", "column"],	["row", "col", "column"],
["minor", "major"],	["minor", "major", "patch"], [1]
["if", "else"],	["if", "else", "elseif", "elif", "elsif"], [2]

• [1]: Cf. semantic versioning.
• [2]: Else if › PHP, Python, Ruby/Perl. "else if" is not possible, right?

Ordinal numeral (Wikipedia)

• Spatial or chronological: ["first", "second", "third", "fourth", "fifth", "sixth", "seventh", "eighth", "ninth", "tenth", "eleventh", "twelfth"],
• Precedence or effect: ["primary", "secondary", "tertiary", "quaternary", "quinary", "senary", "septenary", "octonary", "nonary", "decenary", "undenary", "duodenary"],
• Greek prefix: ["proto", "deutero", "trito", "tetarto", "pempto", "hecto", "hepta", "ogdo", "enato", "decato", "endecato", "dodecato"],
• Numbers: ["zero", "one", "two", "three", "four", "five", "six", "seven", "eight", "nine", "ten", "eleven", "twelve"],
  • And ["un", "dos", "tres", "un pasito pa'delante, Maria", "un pasito pa' atras"], 😂

Note: ChatGPT › quaternary rather than quartary, hecto over ecto, hepta over ebdomo/hebdomo.

Metasyntactic variables (Wikipedia)

Metasyntactic variables used commonly across all programming languages include foobar, foo, bar, baz, qux, quux, corge, grault, garply, waldo, fred, plugh, xyzzy, and thud.

The followings are surely enough: ["foo", "bar", "baz", "waldo", "fred", "toto"],
Note: toto is often used in French.

This could be useful when we don't remember all the names. By typing the last one we know and toggling it to get the next one.

Describe alternatives you've considered

No response

Additional Context

No response

[HiDeoo]

Thanks for your feedback, took me a while to get to it but it's definitely super appreciated. :raised_hands:

I'll try to address each of your points that require a response.

Can you have different lists relative to the current editor/programming language?

Yes, language-specific custom toggles have been added in v0.2.0. Here is the Visual Studio Code reference on how to configure them: https://code.visualstudio.com/docs/getstarted/settings#_language-specific-editor-settings

• ["and", "or"] I think this is a good addition, even outside of programming.

• ["null", "undefined", "NaN", "None", "nil"] I think I would prefer to avoid mixing up different languages in the same toggles and I definitely to not wish to maintain that kind of list myself so if this is something a developer wish to have, I think it's fair to ask them to maintain their own list (either global or language-specific).

• ["map", "reduce", "filter"] I think this kind of change is not so common to be worth adding to the default list.

• ["thead", "tbody", "tfoot"], I think this is a good addition.

• ["dark", "light"] Excellent idea.

• Log levels + success: I was thinking this was a good idea but after thinking about it and trying to find common list, I think it's just impossible to have a list that would be useful for everyone with so many different strategies out there. We'll either have too many items or not enough. I think it's better to let the user maintain their own list.

• ["x", "y", "z"] Good idea.

• ["start", "stop", "end", "pause"] I like the idea but I think having ["start", "stop", "end"] is what I would most expect.

• ["left", "right", "middle", "center", "justify"] I think the left / right toggle should not be expanded and let developers maintain their own list if they wish to have more options based on their language.

• ["head", "body", "foot"] This one was mostly intended for HTML so I think keeping it as is is the best option.

• ["row", "col", "column"] This sounds a bit too specific to me.

• ["minor", "major", "patch"] Good idea.

• ["if", "else", "elseif", "elif", "elsif"] I would prefer to keep it simple and let developers maintain their own list if they wish to have more options based on their language.

• Ordinal numeral: I definitely think this is way too specific and I've never seen this occurred so often that it would be worth even using a toggle for it. If a developer really needs it, they can maintain their own list.

---

Based on your feedback, I've updated the default list to include the changes I've agreed with and released version v0.6.0.

I'm totally conscious that this feels a bit arbitrary, but without many more feedbacks from many users, I try to keep the list as simple as possible while still being useful to most people and it can be hard to find the right balance (that's also why a main goal of the extension is to let users maintain their own list).

Thanks again for your feedback.