-
Notifications
You must be signed in to change notification settings - Fork 2k
fix(examples): css specificity in Tailwind example #10657
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
Conversation
Add 3 new tests to increase coverage from 87.50% to 90.57%: - test_close_with_timeout: Tests the close_with_timeout method - test_client_error_handling: Tests error handling when client fails - test_add_session_id: Tests the add_session_id utility function These tests cover previously untested code paths including timeout handling, error scenarios, and utility functions.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
We used to use a prefix to avoid this but it looks like that was changed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM except for Rust changes
@@ -380,4 +381,115 @@ mod tests { | |||
let payloads = &found[0]; | |||
assert_eq!(payloads.len(), 2); | |||
} | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary?
@tknickman Sigh, they added docs for how to use prefixes now. I've looked at least 10 times over the course of the past N months for this and figured it just wasn't a thing. 🤦 Circling back... |
@tknickman There we are. Thank goodness they brought it back (or made it discoverable). |
Description
As described in #10642, CSS specificity wasn't being handled correctly in the example. This PR fixes it by ensuring the compiled stylesheet from the package:
Testing Instructions
Try it out!