-
Notifications
You must be signed in to change notification settings - Fork 8
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
Storybook navigation broken on mobile #1639
Comments
m-akinc
added
blocked
Blocked on a third-party issue
and removed
triage
New issue that needs to be reviewed
labels
Nov 8, 2023
Blocked on Storybook bug |
Looks like it's resolved in the new mobile UI for Storybook 8.0 - storybookjs/storybook#23723 |
rajsite
pushed a commit
that referenced
this issue
Feb 9, 2024
# Pull Request ## 🤨 Rationale Wanted to see if there were any improvements. ## 👩💻 Implementation - Bumped version from 7.4.0 to 7.6.13 - Had to work around an [issue](storybookjs/storybook#25170) related to the typing of `withActions` decorator of actions add-on. ~~Re-exporting `withActions` from our Storybook utilities file with a type that works (based on [comment in related issue](storybookjs/storybook#22384 (comment) Now providing type argument to generic `withActions` function. - Marked docs support disabled in `addon-essentials` since we import that addon separately (`addon-docs`) so we can configure it. Not sure if this improves anything, but it doesn't seem to hurt. - Also fixes #1639 ## 🧪 Testing Ran Storybook. `npm run storybook` seems to get everything ready about 25% faster (40s -> 30s). ## ✅ Checklist <!--- Review the list and put an x in the boxes that apply or ~~strike through~~ around items that don't (along with an explanation). --> - [x] I have updated the project documentation to reflect my changes or determined no changes are needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🧹 Tech Debt
Looks like for a bit the navigation in storybook has not worked on mobile. We should report it as an issue in storybook / find if an existing issue has been made.
Context: #1635 (comment)
The text was updated successfully, but these errors were encountered: