Skip to content
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(#1216): storybook config #2310

Merged
merged 10 commits into from
Jul 24, 2023
Merged

Conversation

ofhope
Copy link
Contributor

@ofhope ofhope commented Jul 17, 2023

Related to #1216

It looks like Storybook has been set up previously but is currently in a broken state.

I was attempting to explore the project via Storybook and notice the commands weren't working.

Screenshot 2023-07-17 at 9 02 24 pm

The changes in package.json were due to running this command npx storybook@latest init which took me through an install wizard. These are the packages Storybook recommends.

addDecorator, addParameters and withKnobs are no longer supported. Controls are created for you through prop introspection with the ability to override with argTypes.

I'm not familiar with the work prior to these changes so I can't offer garuntee that thats how these stories behaved prior to this upgrade.

But I can confirm all stories are now rendering.

Screenshot 2023-07-17 at 5 40 23 pm Screenshot 2023-07-17 at 5 34 44 pm Screenshot 2023-07-17 at 5 34 41 pm Screenshot 2023-07-17 at 5 34 38 pm

I notice one of the initial motivations were "help reduce bugs and make contributing easier" which I absolutely agree with. It makes debugging hard to reach aspect a breeze. It also helps seperate concerns between stylistic/ux concerns and business logic.

Changes:

I have verified that this pull request:

  • has no linting errors (npm run lint)
  • has no test errors (npm run test)
  • is from a uniquely-named feature branch and is up to date with the develop branch.
  • is descriptively named and links to an issue number, i.e. Fixes #123

@welcome
Copy link

welcome bot commented Jul 17, 2023

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.

@lindapaiste
Copy link
Collaborator

Thank you so much for looking into this! I've never been able to get Storybook to work so I'm uncertain of what it looked like before. It does seem from you screenshots that the components which use styled-components are rendering properly, but the ones that use .scss files aren't getting their styles loaded. Do you have any ideas about loading .scss files? No pressure if you don't, this is still a huge improvement.

stories: ['../client/**/*.stories.(jsx|mdx)'],
addons: [
'@storybook/addon-actions',
'@storybook/addon-docs',
'@storybook/addon-knobs',
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that you removed some packages from the addons array here but kept them in the package.json. Do they need to be kept as dependencies or should they be removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They should be removed now. They've been deprecated https://www.npmjs.com/package/@storybook/addon-knobs

Actions are built in by default. And knobs have been replaced with args and argTypes where you can configure controls to play with. I've updated Buttons and Icons stories to use these rather than the knobs that were there.

}));
export const decorators = [
(Story) => (
<Provider store={store}>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we are connecting to Redux here then maybe we want a way to modify the initial state on a per-story basis? Just a thought. That's something for a future PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what Redux is used for but all components with stories needed it. It could be good to try and remove it as a dependancy from Storybook/Design System components 🤷🏽

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I actually agree. I think of Storybook as being for pure UI components which are not connected to Redux. But the current FileNode and the SocialAuthButton components are connected and they have stories so that's why we need it for now.

Copy link
Collaborator

@lindapaiste lindapaiste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great overall! We do need to fix the eslint setup before merging.

package.json Outdated Show resolved Hide resolved
@ofhope
Copy link
Contributor Author

ofhope commented Jul 18, 2023

@lindapaiste It looks like the css is already built so it was just a matter of including the css file 🎉

import '../client/styles/build/css/main.css'

These screen shots look better

Screenshot 2023-07-18 at 11 32 13 am Screenshot 2023-07-18 at 11 32 15 am

@ofhope
Copy link
Contributor Author

ofhope commented Jul 18, 2023

@lindapaiste so it looks like including the storybook eslint rules in .eslintrc works. It took an eslint restart for it to start prompting with misconfigured stories.

"extends": ["airbnb", "prettier", "plugin:storybook/recommended"],

As a test commenting out the icon stories and looking at the warnings we can see eslint(storybook/default)

The file should have a default export.

Screenshot 2023-07-19 at 9 16 17 am

And if you fix that you get another error about having at least one story.

Screenshot 2023-07-19 at 9 23 25 am

@ofhope ofhope requested a review from lindapaiste July 19, 2023 23:32
@lindapaiste
Copy link
Collaborator

Right now my only concern is the changes in unrelated files due to Prettier. Ideally we want it to pass the linting checks without changing anything. I noticed in your package-lock.json file that there's a minor version bump of prettier and this could be the cause.

Can you try the following steps?

  1. git revert 1c3748d7d349040793ef6c74c168b998f7098262 To rollback the linting changes to FileNode, etc. from this commit.
  2. npm install [email protected] to install the specific version of prettier that we had previously.
  3. npm run lint -- does it pass?

I definitely want to get this merged in ASAP so that we can keep building on it. Now that you've got the basics of Storybook working I'm seeing problems and areas for improvement in the stories and in the components themselves. I've been reading some docs to figure out how to make the most out of Storybook and I've figured out theme switching, selecting icons from a dropdown on the Button story, etc.

label={text('label', 'submit')}
>
{text('children', 'this is the button')}
export const AllFeatures = (args) => (
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The controls on this story don't seem to do anything because we aren't passing down all of the args. Looks like we can write the story as an object with the new "Component Story Format 3". Very cool.

export default {
  title: 'Common/Button',
  component: Button
}

export const AllFeatures = {
  args: {
    children: 'this is the button'
  }
};

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for investigating linting... I mistakenly thought these were linting issues on the main branch. I wasn't giving them much thought. I'll try your suggestion later today and see if I can revert them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah with stories you can set some defaults for all stories. Customise default args per story. Or present them with fixed values too if you like.

Previously this AllFeatures story had dynamic args as knobs and all the reset were fixed.

This is a button story from a personal project where args were overridden.

const Template: Story<ButtonProps> = (args) => <Button {...args} />;

export const FullWidth = Template.bind({});
FullWidth.args = {
  primary: true,
  children: 'Button',
  fullWidth: true
};

@ofhope
Copy link
Contributor Author

ofhope commented Jul 23, 2023

One other addition. I ran npm uninstalled @storybook/addons-knobs this is deprecated.

lindapaiste
lindapaiste previously approved these changes Jul 23, 2023
Copy link
Collaborator

@lindapaiste lindapaiste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 Thank you for all of your work on this!

I'm going to go ahead and merge this. Feel free to keep adding other improvements in additional PRs.

@lindapaiste
Copy link
Collaborator

Ah 💩, one last thing. Can you please commit the package-lock.json file after running npm install [email protected]?

Copy link
Collaborator

@lindapaiste lindapaiste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@lindapaiste lindapaiste merged commit c9b0c4d into processing:develop Jul 24, 2023
1 check passed
@ofhope ofhope mentioned this pull request Jul 24, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants