React-Native: Fixes for v8 compatibility #25678
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shilman
changed the title
shilman
requested review from
yannbf,
ndelangen,
tmeasday,
valentinpalkovic and
kasperpeulen
as code owners
ndelangen
approved these changes
Jan 23, 2024
5 tasks
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes N/A
What I did
PreviewWithSelectionwhich was accidentally (?) removedgetStoryContextreact-nativeentry points forpreview-api/manager-api🦋 Canary release
This pull request has been released as version
0.0.0-pr-25678-sha-560d4141. Try it out in a new sandbox by runningnpx storybook@0.0.0-pr-25678-sha-560d4141 sandboxor in an existing project withnpx storybook@0.0.0-pr-25678-sha-560d4141 upgrade.More information
0.0.0-pr-25678-sha-560d4141shilman/rn8560d41411705929286)To request a new release of this pull request, mention the
@storybookjs/coreteam.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=25678