Skip to content
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

fix: Fix missing & in Tailwind CSS hover selector in MintComponent.tsx #1879

Closed
wants to merge 1 commit into from

Conversation

fragchain
Copy link

What changed? Why?

I noticed a issue in the selector [&_button]:hover:bg-[#014ceb]. The & symbol was missing before hover, which is required for proper Tailwind CSS syntax. I've corrected it to [&_button]:&hover:bg-[#014ceb] to ensure it works as intended.

Copy link

vercel bot commented Jan 26, 2025

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

Name Status Preview Comments Updated (UTC)
onchainkit-coverage ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2025 0:42am
onchainkit-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2025 0:42am
onchainkit-routes ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2025 0:42am

Copy link

vercel bot commented Jan 26, 2025

@fragchain is attempting to deploy a commit to the Coinbase Team on Vercel.

A member of the Team first needs to authorize it.

@cpcramer
Copy link
Contributor

Thanks for the contribution!

@@ -28,7 +28,7 @@ export default function MintComponent() {
<NFTCreator className="-mt-1 pt-0" />
<NFTMedia />
<NFTCollectionTitle />
<NFTMintButton className="[&_button]:bg-[#0052ff] [&_button]:hover:bg-[#014ceb] [&_button]:active:bg-[#0148dc] [&_button]:disabled:bg-[#80a8ff]" />
<NFTMintButton className="[&_button]:bg-[#0052ff] [&_button:hover]:bg-[#014ceb] [&_button:active]:bg-[#0148dc] [&_button:disabled]:bg-[#80a8ff]" />
Copy link
Contributor

@brendan-defi brendan-defi Jan 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cpcramer this doesn't look right to me.

Here's the tailwind docs:
image

IIUC, the brackets go around the arbitrary variant, but do not include the active state.

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

Successfully merging this pull request may close these issues.

4 participants