pwa-studio
pwa-studio copied to clipboard
Update storybook/react
Description
TODO: Describe your changes in detail here.
Related Issue
Closes #ISSUE_NUMBER.
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist
- I have added tests to cover my changes, if necessary.
- I have added translations for new strings, if necessary.
- I have updated the documentation accordingly, if necessary.
Fails | |
---|---|
:no_entry_sign: | A version label is required. A maintainer must add one. |
:no_entry_sign: |
No linked issue found. Please link a relevant open issue by adding the text "closes #<issue_number>" or "closes JIRA-<issue_number>" in your PR. |
:no_entry_sign: | Missing information in PR. Please fill out the "Description" section. |
Warnings | |
---|---|
:warning: | Found the word "TODO" in the PR description. Just letting you know incase you forgot :) |
Messages | |
---|---|
:book: | DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed). |
:book: |
Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete. |
If your PR is missing information, check against the original template here. At a minimum you must have the section headers from the template and provide some information in each section.
Generated by :no_entry_sign: dangerJS against 973f900c719bf72522cc3ef9262350d77e2f2175