all 21 comments

sorted by: hot top controversial new old
[–] 16 points 3 years ago (2 children)

I can't tell if it's a parody or an actual genius idea.

  • source
  • hideshow 4 child comments
  • [–] 3 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago*

    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.

  • source
  • parent
  • [–] 9 points 3 years ago

    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.

  • source
  • [–] 8 points 3 years ago

    It looks neat, but I think I'll keep my true and false. I don't like chhannngggeeee!

  • source
  • [–] 4 points 3 years ago

    Ngl I dont hate it.

  • source
  • [–] 4 points 3 years ago (1 child)

    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 assigning x = true? Bring it on.

  • source
  • hideshow 2 child comments
  • [–] 2 points 3 years ago (3 children)

    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.

  • source
  • hideshow 6 child comments
  • [–] 0 points 3 years ago (1 child)

    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; to true or something like that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)
  • [–] 0 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    You know, I could find a few cases where this could have helped me troubleshoot stuff on the code.

  • source
  • [–] 1 point 3 years ago

    Grep -Irn "green toggle thingy" ./*

  • source
  • [–] 1 point 3 years ago

    Sounds idiotic and like spaghetti code likely.

    Why?

  • source