No there is AT LEAST one use for this. You could create an options class with booleans, and you could toggle settings when running or debugging. Also less savvy people (other non software engineers) can toggle settings easier for internal tools.
fwiw I opened an issue on the vs code repo. It already got a downvote and the issue was reassigned from one maintainer to another. Popcorn is tightly secured.
Previously I was able to search for “true” and “false” in my codebase. How do I do that now?
VS Code has a new search interface specifically for toggles. It’s closed by default, but you can open it by clicking the “Toggle Search Toggle” toggle.
Yo dawg, I heard you liked toggles so we gave you a toggle to search for toggles in your toggle
Also, the section defining behaviour for null and undefined values are kind of bonkers.
Buuut, a nice visual nonetheless. I don't see myself using it though.
I used an extension a while ago that changed CSS colour values (#ababab) into little coloured dots, that became a colour picker when clicking on them (while still letting you input RGB or Hex, ofc), and it was pretty awesome!
So, I could unironically see this being really nice. Although... I think this would need a pretty narrow context, something like if x == true would look pretty confusing as a toggle, I imagine. But assigningx = true? Bring it on.
Good point. I actually thing that having if x == true is bad practice anyway because it's redundant, so showing a toggle in that context would have the benefit of highlighting that something's wrong.
I, uh, actually kind of like the idea. If you just visually converted primitives to a toggle after you type true/false, and let you delete it like any other text, it could be a small convenience on any flags you might change during the development process.
Oh, I could easily see a trainwreck of an implementation. But if this was just a display option like color coding keywords and variables, but you could click to change the underlying true/false? I might add it.