• luciole (he/him)@beehaw.org
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 years ago

    News flash: your snark makes you an unpleasant person. Read my comment again. I said tree shaking fixes this… unless you don’t know what content you’ll display and what classes you’ll need at build time. Not all sites are static.

    • AnarchoYeasty@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 years ago

      Unless you are going to be allowing custom html to be added the tooling is smart enough to figure out what possible classes your code can use. You’d have to do something dumb to not have the tools able to tell what components you are serving.

      • luciole (he/him)@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 years ago

        More generally, the more you have a flexible editor in the app, the worst it gets. This is the use case where I ran into trouble.

        • AnarchoYeasty@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          edit-2
          2 years ago

          Make an element that is hidden that has all possible values of classes you can use. Or use normal css for that one part of your app if that isn’t possible. Lots of ways you can handle this without thinking the framework doesn’t work.

          Ninja:

          https://tailwindcss.com/docs/content-configuration#safelisting-classes

          Tailwind actually has this use case covered already. Use the safe list functionality to always include the classes you need.