Pre-defined transform without matcher logic

[TrevorRice]

Apologies if I missed this in the docs, but is there an easy way to leverage a pre-defined transform without the built-in matcher logic?

For reasons I'm not privy to, our team opted to use colors instead of color when defining our tokens. This means, for instance, when running our tokens through ios-swift-separate, the color/UIColorSwift transform is not applied because isColor does not match our colors category.

I know I could rework/reorganize some things, but I'm hoping to avoid reimplementing color/UIColorSwift (and pulling in its dependency) simply to apply the transform to our colors category instead of color.

[jorenbroekema]

Hm no this is currently not possible, transforms aren't exposed publicly without the attached matcher/filter (called filter in v4).

I'd be open to making the transforms themselves available without the filters though, feel free to raise an issue and I'll mark it as enhancement

You can kinda do it in v4:

const colorHslBuiltin = StyleDictionary.hooks.transforms['color/hsl'];
StyleDictionary.registerTransform({
  ...colorHslBuiltin,
  filter: (token) => token.type === 'colors',
  name: 'colors/hsl', // if you don't override the name it will register on the original name and override the built-in one, which might be nice
});

[TrevorRice]

Interesting! Thanks, I'll play around with this.