While Testing the website We can get so many errors. While loading components we facing so many issues. storybook inside the project directory helps us to find the components present in it and are the mounting or not. This is will help the developers or contributors.
How Has This Been Tested?
Set-up the Project.
Inside the root folder Go to /src/stories/CodeFeed/ExploreOrg/
There you will find index.stories.jsx file.
Inside This Make sure That import Should be like below
import ExploreOrg from "../../../components/MyFeed/discoverOrgs/OrgExplore";
Now Run the below command in root folder
npm run storybook
-Make sure remaining commands are running provided in contribution guide
You will find the bug fixed as below image.
Screenshots or GIF (In case of UI changes):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Updating the index.stories.jsx. because of incorrect import storybook shows error. while opening the card/ Card-Tabs. Now I fixed it.
Description
Related Issue
Wrong path file in Codelabz-final/src/stories/CodeFeed/ExploreOrg/index.stories.jsx resolve #35
steps to reproduce
-Make sure remaining commands are running provided in contribution guide
-You will see below error
Link of the Issue
https://github.com/c2siorg/Codelabz/issues/35
Motivation and Context
While Testing the website We can get so many errors. While loading components we facing so many issues. storybook inside the project directory helps us to find the components present in it and are the mounting or not. This is will help the developers or contributors.
How Has This Been Tested?
Set-up the Project.
Inside the root folder Go to /src/stories/CodeFeed/ExploreOrg/
There you will find index.stories.jsx file.
Inside This Make sure That import Should be like below
Now Run the below command in root folder
-Make sure remaining commands are running provided in contribution guide
You will find the bug fixed as below image.
Screenshots or GIF (In case of UI changes):
Types of changes
Checklist: