-
Notifications
You must be signed in to change notification settings - Fork 3
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(components): remove built-in border radius #922
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Lighthouse Report✨ https://blog-3ntqt4qls-sabertaz.vercel.app/🚀 Vercel preview deployment
✨ https://blog-3ntqt4qls-sabertaz.vercel.app/posts🚀 Vercel preview deployment
✨ https://blog-3ntqt4qls-sabertaz.vercel.app/tags🚀 Vercel preview deployment
✨ https://blog-3ntqt4qls-sabertaz.vercel.app/books🚀 Vercel preview deployment
✨ https://blog-3ntqt4qls-sabertaz.vercel.app/about🚀 Vercel preview deployment
|
Codecov Report
@@ Coverage Diff @@
## main #922 +/- ##
=======================================
Coverage 99.41% 99.41%
=======================================
Files 175 175
Lines 1022 1024 +2
Branches 84 84
=======================================
+ Hits 1016 1018 +2
Misses 5 5
Partials 1 1
Continue to review full report at Codecov.
|
3366be3
to
ee78769
Compare
ee78769
to
e420c9a
Compare
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
Pull Request
This PR Contains
Motivation / Use-Case
Test-Case
I have verified these changes via:
Breaking Changes
Additional Info