-
Notifications
You must be signed in to change notification settings - Fork 286
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 the RRM SetupMain story and include a VRT scenario. #9082
Conversation
Build files for 5e0d539 have been deleted. |
Size Change: 0 B Total Size: 1.67 MB ℹ️ View Unchanged
|
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.
Thanks @techanvil, just a few small things to update
@@ -27,8 +32,27 @@ function Template() { | |||
|
|||
export const Default = Template.bind( {} ); | |||
Default.storyName = 'Default'; | |||
Default.scenario = { | |||
label: 'Modules/ReaderRevenueManager/Setup/SetupMain/Default', | |||
delay: 250, |
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.
We already have a base delay
in our backstop config which is much more – does this actually help or is it just copied?
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.
Hmm - fair question. The story does have a brief loading state so I thought we might need the delay. But, maybe the default will suffice. I've removed the delay, let's see how it fares.
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.
To be honest, I had forgotten the default is 1 second which as you say is much more and will probably be enough.
@@ -27,8 +32,27 @@ function Template() { | |||
|
|||
export const Default = Template.bind( {} ); | |||
Default.storyName = 'Default'; | |||
Default.scenario = { | |||
label: 'Modules/ReaderRevenueManager/Setup/SetupMain/Default', |
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.
We should avoid hardcoding the label
as this is constructed based on other values such as the storyName
and the default title
below.
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.
Thanks - another interesting comment. Most of our stories do specify the label, but you are quite right, it shouldn't be needed.
In fact I've only found one scenario without a label in the codebase (it's one that you updated recently to remove the label :)).
Default.scenario = {}; |
Anyhow - another good shout, I've removed the label. Again, it would be nice to tidy the existing stories up at some point in this regard.
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.
Yeah, I did some analysis recently and found that there are a lot of stories where the generated scenario label differed from the one explicitly referenced but yeah it would be nice to clean that up.
.receiveGetPublications( [] ); | ||
|
||
return ( | ||
<WithTestRegistry registry={ registry }> |
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.
Please use WithRegistrySetup
and the setup func
instead – we should almost never need WithTestRegistry
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.
Thanks for the reminder! I had forgotten this, and mostly copied the decorator from one of the existing stories which use WithTestRegistry
, e.g.:
site-kit-wp/assets/js/components/Header.stories.js
Lines 286 to 300 in 7705f0c
export default { | |
title: 'Components/Header', | |
component: Header, | |
decorators: [ | |
( Story ) => { | |
const registry = createTestRegistry(); | |
provideSiteInfo( registry ); | |
return ( | |
<WithTestRegistry registry={ registry }> | |
<Story /> | |
</WithTestRegistry> | |
); | |
}, | |
], |
Anyhow - good to be reminded, I've updated the story!
It would be nice to go through the existing stories at some point with a view to tidying them up in this regard...
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.
Great, thanks!
Summary
Addresses issue:
<PublicationSelect>
component #8837Relevant technical choices
PR Author Checklist
Do not alter or remove anything below. The following sections will be managed by moderators only.
Code Reviewer Checklist
Merge Reviewer Checklist