Add safe list definitions for components to ensure correct display when CSS generated locally

Hello @paddy_deburca

Thanks for posting this issue.

I understand the need as in branch 4.0.x I used the safelist key in tailwind.config.js to address that.

At that time, I first added comments including explicit classes, in all twig files where those classes were created dinamically. I was really not happy with that, so when I found the safelist, I used it right away as I prefered an "all in single file" solution.

That being said, you'll understand I don't want to create many additional twig files to address that. What I will do is following the current recommendation of the creator of Tailwind :

... I would just recommend creating a safelist.txt file somewhere that has all the classes you want to safelist and Tailwind will automatically scan that and include them. ...

(cf. )https://github.com/tailwindlabs/tailwindcss/discussions/14462#discussion...).

I'm not sure what solution to implement:

• Provide this safelist file in the theme
• OR document it ...

@g4mbini,

I have consolidated the individual safest files into one Twig file that can be stored with the theme (possibly root folder).

I have tried to complete the file with all the class names used by DaisyUI v5 (beta).

Paddy.

Hello @paddy_deburca

Can you provide a MR with the file safelist.txt containing all necessary class in /assets/compilation/ folder ?

And maybe add some documentation in section "Manually: install Tailwind CSS, DaisyUI with NPM" at https://git.drupalcode.org/project/ui_suite_daisyui/-/blob/5.0.x/README.... ?