@argyleink following on from our discussion on #423, I wanted to make sure of a couple of things first.

In my over simplified understanding about the work @jeffposnick started on #423, the /^op-color-(.*)$/ rule converts an OP prop into an atomic CSS class using the token's value var(--violet-4)?

op-color-violet-4 {
  color: #9775fa;
}

More rules in the preset would extrapolate OP custom properties into its respective atomic CSS classes.

Atomic CSS Class Prefix

What do you think of having the atomic class prefix be configurable via the preset, but we also provide a default to op?

EDIT: Thinking about the default some more I realised some folks might not want a prefix at all! Maybe the default is to not have a prefix? Prefix could be useful if you have a CSS class name clash; maybe you're using OP with Tailwind or something. The inverse of this is that when there isn't a likelihood of a name clash, then omitting the prefix makes sense.

import { defineConfig } from 'unocss'
import openPropsPreset from "open-props/presets/uno";

export default defineConfig({
  presets: [
    openPropsPreset({
      prefix: 'ops', // default value is 'op'
    }),
  ],
})

ops-color-violet-4 { }

op-color-violet-4 { }

It's lines up nicely with the customisability of a build. The following taken from the docs

TODOs

Here is a list of todo items with the one's Jeff addressed and of which is still to be done

Adapter for Uno #406

Description

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions