-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Document --spacing #2215
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.
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
Comments
This comment has been minimized.
This comment has been minimized.
The pages that use --spacing show it like your screenshots but there's no place with a list of all those pages. https://tailwindcss.com/docs/theme#theme-variable-namespaces says |
@kocv59 I understand the motivation but I'm not sure about the practicality of what you're suggesting. When we work on adding new utilities we usually only update the page of the specific utility so it I worry that it would make things a bit complex to have to remember to add all the backlinks to another page. I'm curious why you want an exhaustive list for this, though? |
If you want to change the --spacing number you know all the places to look where to see the changes.
It's more complex for all users to click on all the utility pages and see if --spacing is anywhere in the page instead of developers changing it once in rare cases new utility that uses --spacing is added. If you add a new utility that uses --spacing you only need to make one change to the list of --spacing utilities to add link to the new page for the new utility. What more backlinks are there? |
I think this only needs to be learned once. Perhaps an instructional post could be published about it. In this case, I'm thinking of either:
|
It doesn't need to be dynamic. A manually created documentation page that is updated occasionally would suffice, as new utilities utilizing Ideally, each utility would have the ability to override |
Theme documentation says --spacing is used for px and max-h but not the others. A list of all utilities that use it should be somewhere on the page.
The text was updated successfully, but these errors were encountered: