Skip to content

Document supported data types for arbitrary and bare values in custom functional utilities #2310

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

marcoschndlr
Copy link

@marcoschndlr marcoschndlr commented Jul 20, 2025

Add documentation for the supported data types of arbitrary and bare values in custom functional utilities.
Previously, it was not clear which data types are supported when declaring a custom functional utility.
Especially when declaring a utility with arbitrary values as this silently fails.

The supported data types for arbitrary values are taken from here:
https://github.com/tailwindlabs/tailwindcss/blob/939fda6f4e101ff3d378e0d51c20a8baa229afff/packages/tailwindcss/src/utils/infer-data-type.ts#L5-L22

Bare values from here: https://github.com/tailwindlabs/tailwindcss/blob/939fda6f4e101ff3d378e0d51c20a8baa229afff/packages/tailwindcss/src/utilities.ts#L5731-L5739

Closes #2176

Add documentation for the supported data types of arbitrary and
bare values in custom functional utilities.
Previously, it was not clear which data types are supported when
declaring a custom functional utility.
Especially when declaring a utility with arbitrary values as this
silently fails.

Closes tailwindlabs#2176
Copy link

vercel bot commented Jul 20, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
tailwindcss-com ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 20, 2025 6:56pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document data types for functional utilities
1 participant