I can’t tell if it’s a parody or an actual genius idea.
I would like to see the debugger give a list of all these boolean values and watch them toggle in real time. That would be far more useful.
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.
Eh, I’ll stick with C# slowly becoming more and more syntax-redundant like all the other OOPLs :'(
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.
It looks neat, but I think I’ll keep my
trueandfalse. I don’t like chhannngggeeee!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, 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.
I mean this as a joke but you might be right. A quick search suggests that no one implemented something like this yet.
As long as it’s not literally a toggle that you can interact with.
I can only imagine the horrors of accidentally clicking in the editor while selecting some text and quietly changing
certificateIsValid = false;totrueor something like that.Nah, make it a keybind like alt-shift-click and give it a deafening sound like throwing an industrial breaker.
As a visual indicator, sure.
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.
More technical details in the full article ;)
Beatiful. Magnificent indeed
To actual posisble implementations, it’d actually be interesting as an indicator next to the bool to make it easier to see when debugging
Ngl I dont hate it.
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 == truewould look pretty confusing as a toggle, I imagine. But assigningx = true? Bring it on.Good point. I actually thing that having
if x == trueis bad practice anyway because it’s redundant, so showing a toggle in that context would have the benefit of highlighting that something’s wrong.
You know, I could find a few cases where this could have helped me troubleshoot stuff on the code.
Grep -Irn “green toggle thingy” ./*
