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

Named exports for all components #241

Merged
merged 2 commits into from
Feb 27, 2025

Conversation

ohp-inmeta
Copy link
Contributor

Describe your changes

Storybook is not too happy with default exports, so the code-examples gave strange component names. Added named exports to all components, and updated all stories.

Updated Storybook to 8.6

Checklist before requesting a review

  • I have performed a self-review and test of my code
  • I have added label to the PR (major, minor or patch)
  • If new component: Is story for component created in stories-folder?
  • If new component: Is README-file for CSS documentation created and added to the story?
  • If new component: Is tsx-file import added to packages/react/index.tsx?
  • If new component: Is CSS-file added to packages/css/index.css?

Storybook is not too happy with default exports, so the code-examples gave strange component names. Added named exports to all components, and updated all stories.

Updated Storybook to 8.6
@ohp-inmeta ohp-inmeta requested a review from a team as a code owner February 26, 2025 11:14
Copy link
Contributor

Please set a versioning label of either major, minor, or patch to the pull request.

@ohp-inmeta ohp-inmeta linked an issue Feb 26, 2025 that may be closed by this pull request
@ohp-inmeta ohp-inmeta merged commit 0331042 into main Feb 27, 2025
3 checks passed
@ohp-inmeta ohp-inmeta deleted the feature/229-named-exports-update-storybook branch February 27, 2025 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Storybook - bug with component names in code examples
2 participants