3 ms·

css syntax highlighting has been broken in vs code for years now. how in the world is this possible in THE web dev editor?

• adzm 9mo ago
  How is it broken? I'm looking at it working fine right now.
  • jazzyjackson 9mo ago
    Not OP but I remember working on a team that just put up with nonhighlighted nonintelligent CSS because it was embedded in a handlebars template. Of course there is an extension that's supposed to fix this but it was flaky and broke often. An easy fix was to move CSS to a separate file for import but that was a big change for these guys.
  • publicdebates 9mo ago
    Not GP, but he's absolutely right, it's been pissing me off for years now. Only thing I can remember off the top of my head is nested selectors still not highlighting properly. They partially fixed this a few months ago but that's it. I guess we're all waiting on GHCP to prioritize and fix it now?
    • css_apologist 9mo ago
      nested is the main one, however i remember cases where a rule couldn't be parsed and the rest of the file went fuckidy this is pathetic, and really shows how much of a shitter css tooling currently resides in
      • jtbaker 9mo ago
        Insert obnoxious tailwind comment
        • jtbaker 9mo ago
          I feel bad about this comment as of today's news. I love tailwind and feel like it has supercharged my ability to be productive with CSS, but recognize that it can be overprescribed.