[Storybook] Add stories for more components (letters R-S) - Part 4#7733
Conversation
There was a problem hiding this comment.
[just me thinking out loud] I sometimes wonder how much value consumers get from us exporting subcomponents like this, vs just the higher level components 🤔
There was a problem hiding this comment.
It can have value to understand what's available, how it works etc. Or even to maybe reuse some components in other contexts even if unexpected? 🤔
cee-chen
left a comment
There was a problem hiding this comment.
Minor nav bar organization
- which is its own separate style
db10dd3 to
6b8eb75
Compare
cee-chen
left a comment
There was a problem hiding this comment.
Pushed up a minor fix for undefined step status being valid for EuiStepNumber and EuiStep (but not EuiStepHorizontal 🤷), other than that this looks great!
|
Preview staging links for this PR:
|
💚 Build Succeeded
History
|
|
|
||
| const meta: Meta<EuiStepNumberProps> = { | ||
| title: 'Navigation/EuiSteps/EuiStepNumber', | ||
| title: 'Navigation/EuiSteps/Subcomponents/EuiStepNumber', |
There was a problem hiding this comment.
Hmm, if I remember correctly, we had a discussion some time ago about nesting conventions and agreed that we nest subcomponents under the components based on component name and that we wouldn't add other folders as that might be confusing? (conversation)
So the idea would be that EuiStepNumber is a subcomponent of EuiSteps (or even EuiStep) so it's nested under those.
Next to other components the naming Subcomponents now would mean there is a component called Subcomponents if we go by how we organized components so far 😅
Summary
closes #7482
This PR adds more stories for components with the letter S:
Additionally adds base VRT reference images based on the added stories.
QA