DEFAULT theme keys being lowercased

[davidkelley]

Hi,

Thanks for a great library. I'm in the middle of implementing this for our theme, but have noticed that the DEFAULT keyword is being lowercased inside the output. Tailwind needs this to be uppercased, so that we can make use of class names such as bg-orange for example. Are you able to help?

tailwindlabs/tailwindcss.com#1114
https://v2.tailwindcss.com/docs/upgrading-to-v2#update-default-theme-keys-to-default

[nado1001]

Hi, @davidkelley
Thank you for raising the great issue!
The "DEFAULT" theme key is now supported in version 1.3.2.
Please update your package version and check it.
We are also testing this on the example, so you can check it out in conjunction with the example if you like.

[davidkelley]

Thanks very much @nado1001. Really useful library, great work!

[3CordGuy]

Sorry to resurrect a closed issue, but I don't see this working on the latest version when outputting individual theme files. Seems like the original keys are used (not transformed keys).

For example if I do a transform like this:

StyleDictionary.registerTransform({
  type: 'name',
  name: 'upperDefault',
  matcher: token => token.name.includes('default'),
  transformer: prop => {
    let u = prop.path
      .map(part => {
        if (part.includes('default')) {
          return part.toUpperCase();
        }
        return part;
      })
      .join('.');

    return u;
  },

The output still used the path and not the new name transform which has "DEFAULT" in the new name.

[nado1001]

@3CordGuy
Sorry for the delay in noticing the issue.
Can you show us the whole source code in your repository, codesandbox, etc., so that we can get a better understanding of the issue here?

[3CordGuy]

I ended up rolling with another solution. Thanks for responding, though. I appreciate you putting this library out there.