• expr@programming.dev
    8·
    12 hours ago

    I’m honestly not sure, but I’m fairly certain it’s intentional obfuscation done for the production build. Why they think it’s so important to hide class names, I’ll never know.

    • yumyampie@lemmynsfw.com
      4·
      8 hours ago

      It is not intentional. The tooling needs to generate a short unique id to prevent css name clashing.

      During development 2 developers can write the same css class name in two seperate places:

      • developer A: .container { padding: 8px } at dashboard
      • developer B: .container { padding: 32px } at sidebar

      Without this tooling developer need to find ways to prevent name clashing:

      • .dashboard__container
      • .sidebar__container

      and they need to do this for every class name.

      with this tool, developer don’t have to worry about this ever, continue using .container and it get generated into:

      • .aP2be7
      • .7aFrJp