[BUG] Adding nested color in tailwind.config triggers `tailwindcss/no-custom-classname` warning

[boompikachu]

Describe the bug
Adding nested color in tailwind.config triggers tailwindcss/no-custom-classname warning

To Reproduce
Steps to reproduce the behavior:

1. Add the following to tailwind.config file

colors: {
    transparent: 'transparent',
    current: 'currentColor',
    white: '#FFFFFF',
    black: '#000000',
    example: {
      1: '#F0f025',
    },
    category: {
      example: {
        1: '#F0F025',
      },
    },
}

2. Add text-category-example-1 to className

Expected behavior
Should not trigger eslint warning

Screenshots
This doesn't work

This works

Environment (please complete the following information):

• OS: macOS
• Softwares + version used:
  • VSCode 1.67

Additional context
Add any other context about the problem here.

eslint config file or live demo
By providing a link to a live demo, a demo video or a github repo fixing the issue will be easier.

[francoismassart]

WIP on #132

[francoismassart]

@boomikuma I just published a beta version with the fixes listed on #132
https://github.com/francoismassart/eslint-plugin-tailwindcss/tree/fix/no-custom-classname-plugin-support#readme

npm i eslint-plugin-tailwindcss@3.6.0-beta.1

Please give it a try and provide feedback and or issues 👍
Thank you

[francoismassart]

Should be fixed in the latest release 3.6.0

Make sure to:

1. Update the eslint-plugin-tailwindcss package
2. Restart your editor
3. Report any issue on this repo

[damianobarbati]

@boompikachu how did you solve this problem? I still see this today, my custom colors trigger the error