Repository navigation
Add suggestions for named opacity modifiers - #20287
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughIn 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
Confidence Score: 5/5Safe to merge — changes are additive and confined to IntelliSense metadata; no runtime CSS generation logic is touched. The change is a narrow, mechanical addition of No files require special attention. Reviews (3): Last reviewed commit: "update integration tests" | Re-trigger Greptile |
Now that we suggest modifiers based on the `--opacity` namespace, these upgrades can stay the same.
This PR re-enables suggestions for named opacity modifiers that can be configured via the
--opacity-*namespace.Before we launched v4, we got rid of this feature: #14278 & #14339
But later we re-added the feature, without updating intellisense suggestions: #15009
This PR re-adds suggestions for utilities that read from the
--opacity-*namespace for named modifiers. A lot of utilities use some internal abstraction that get this for free once we use thecolorUtilitysetup, but some utilities don't use these, and I had to add the--opacitymodifier theme key manually.Fixes: tailwindlabs/tailwindcss-intellisense#1541
Test plan
--opacity-*namespaceBefore:

After:
Notice that the
/foosuggestion is available