-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
✔️ Deploy Preview for basestore ready! 🔨 Explore the source changes: 49880a1 🔍 Inspect the deploy log: https://app.netlify.com/sites/basestore/deploys/622b6951a629fd0009914985 😎 Browse the preview: https://deploy-preview-381--basestore.netlify.app |
Preview is readyThis pull request generated a Preview👀 Preview: https://preview-381--base.preview.vtex.app |
Gatsby Cloud Build Reportbasestore 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 8m PerformanceLighthouse report
|
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!
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.
Good Job! ✨
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.
Good!
What's the purpose of this pull request?
To not compromise the semantic meaning of
Badge
variants usage, I suggest renaming the variants with a general purpose.BadgeVariants = 'neutral' | 'info' | 'highlighted'
For the product card context, the previous options ('outOfStock' | 'new' | 'recommended' | 'neutral') suit very well . But we are also using the Badge in different contexts such as CartSidebar, Filter, Suggestions.
How does it work?
Nothing changes visually.
Some examples of current use:
Badge variant="neutral"
Badge variant="info"
How to test it?
Badges
colors on Filters and CartSideBar remains the same as http://base.vtex.appReferences
Checklist
You may erase this after checking them all ;)