WordPress / WordPress/openverse
Completely eject from nuxt storybook
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 380
- Forks
- 290
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 8
Description
Problem
We've ejected from nuxt storybook so that we can modify the configuration, but even after doing that the configuration still relies on the .storybook folder generated by nuxt storybook. This creates complications in our tool chain.
Description
Let's move away from Nuxt storybook entirely.
Kudos to @dhruvkb for suggesting this here: https://github.com/WordPress/openverse-frontend/pull/1139#issuecomment-1072448019
Implementation
- 🙋 I would be interested in implementing this feature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing .storybook folder and the configuration that still relies on Nuxt Storybook. Trace how Nuxt Storybook generates or supplies that configuration, then define completion as removing that dependency while preserving the project's Storybook setup; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100