Replies: 1 comment
-
|
This feature will also help in enhancing collaboration for frontend shared libraries. I can accept changes to a component from another developer, and display the status that changes have been added but not verified. And then when it is verified, it can display status as verified which means it is stable, and available to use. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
Working on many dozens of components with 3-5 stories each and having work split up across design, frontend dev and backend teams as well as a QA process. For me as a backend dev it's hard to keep track of which components I have finished, where I have pending todos, and what still needs to be done. Of course there's external tools in place like confluence/jira/trello/discussions on figma etc. but: we consider storybook to be the ultimate truth of CSS/JS/HTML and I'd wish I could use it to track statuses of sections/components and individual stories in there, too.
When a backend developer starts implementing a component into a CMS, we don't want the frontend devs to make changes to argument names, types, etc. anymore. So if a specific color indicates this is in progress by a backend dev, he knows not to touch it. The other way around, could be helpful too, a designer makes a change, indicates it with a specific color, so everybody else instantly knows they need to take a look/make adjustments.
This would help overall transparency, so that I can quickly see what others are doing, and which component QA accepted, and which ones need modifications.
It would also improve my life as sometimes I jump between components depending on urgency or co-dependencies. Marking a component in a specific state (color) would make my life easier seeing instantly what still requires my attention.
Describe the solution you'd like
It would be great if I was able to flag the status for folders, components and stories in a easy fashion.
Ideally, it would be possible so that configurable areas (eg: design, frontend, backend, Q&A) could have their own flags.
Describe alternatives you've considered
all the other channels of communication/version control/etc. we use. their disadvantage: they take away my focus, require logins, etc.
Are you able to assist to bring the feature to reality?
no
Additional context
Maybe something like this already exists, and I simply don't know about it. I know there are tag one can assign to stories.
I just would prefer having a "one-click" way of doing this.
Beta Was this translation helpful? Give feedback.
All reactions