Skip to content

Add explanation for programmatically composed class names to use the safelist option #233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flavorjones merged 1 commit into from
Dec 13, 2022
Merged

Add explanation for programmatically composed class names to use the safelist option #233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Add explanation for programmatically composed class names to use the … 
…safelist option.
  • Loading branch information
@elalemanyo
elalemanyo committed Dec 12, 2022
commit 9b01bf57cdf1f49e202ac765d78a43d741e2eaae
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,8 @@ Tailwind uses modern CSS features that are not recognized by the `sassc-rails` e

### Class names must be spelled out

For Tailwind to work, your class names need to be spelled out. They can't be programmatically composed. So no "text-gray-#{grade}", only "text-gray-500".
For Tailwind to work, your class names need to be spelled out. If you need to make sure Tailwind generates certain class names that don’t exist in your content files or they are programmatically composed, use the [safelist option](https://tailwindcss.com/docs/content-configuration#safelisting-classes).


### ERROR: Cannot find the tailwindcss executable for <supported platform>

Expand Down