-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: Adjust Alert for CMS #31
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Preview is readyThis pull request generated a Preview👀 Preview: https://sfj-8923df7--nextjs.preview.vtex.app |
Lighthouse ReportsHere are the Lighthouse reports of this Pull Request📝 Based on commit 8923df7
|
Remember to add a new entry to the changelog. |
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.
Nice. Just a minor comment
What's the purpose of this pull request?
This PR will replicate the changes made in this gatsby.store PR.
How does it work?
The
Alert
(in thesrc/common/Alert
folder) will get the propertiesicon
,text
,linkText
,actionLink
anddismissible
, instead of just receiving everything as children (and hardcoded, like theicon
and thedismissible
properties)How to test it?
Nothing special to be tested, the
Alert
will be displayed exactly as before. It will just make the props available, so we can use them in a future PR in storeframework.store.References
Related Jira task
Checklist
Added an entry in the
CHANGELOG.md
at the beginning of its due section. The latest version should come first.Added the PR number with the PR link at the entry in the
CHANGELOG.md
. E.g., New items in thepull_request_template.md
(#4)PR description
Added a label according to the PR goal -
Breaking change
,Enhancement
,Bug
orChore
.Added the component, hook, or pathname in-between backticks (``) - If applicable. E.g.,
ComponentName
component.