-
-
Notifications
You must be signed in to change notification settings - Fork 651
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
Upgrade to React Native v63. #4420
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d346073
ComposeBox [nfc]: Say a more accurate thing in a TODO.
chrisbobbe 17d9285
ComposeBox [nfc]: Un-export a function that's clearly local.
chrisbobbe df56386
types: Relocate some `$FlowFixMe`s and correct their TODOs.
chrisbobbe 86e6349
deps: Point to PR commit for @react-native-community/cameraroll.
chrisbobbe bcc1356
deps: Upgrade to React Native v0.63.
chrisbobbe 6d6a3d8
podfile [nfc]: Set up Flipper Pods by calling a function exposed by RN.
chrisbobbe 0119399
presenceReducer [nfc]: Point to the right Flow bug in two fixmes.
chrisbobbe File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One change here is that this particular pod no longer gets included. The upstream function has this:
and
production
defaults tofalse
.I'm not sure what that does. It sounds like something that's good to leave out in release builds, but we might miss in dev builds. But I guess if things still seem to work well in development, then we didn't need it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since
production
defaults tofalse
, and we don't take it away from the default (which we would do by passing an argument with ouruse_react_native!
call in the Podfile), I think this pod is still included in all builds.unless false
is equivalent toif true
, I think. Is that right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just changed it to
unless true
in node_modules and runpod install
(viayarn
), and I see a line withReact-Core/DevSupport
removed fromPodfile.lock
.(The
/
says to look forDevSupport
as a "subspec" ofReact-Core
. I think all subspecs ofReact-Core
would normally have been pulled in by thepod 'React-Core'
line, above this conditional—but this isn't happening here becauseReact-Core
's podspec declares a "default subspec"; doc.)Probably best to keep pulling in
DevSupport
for development, but I agree that it should be fine to exclude it in production builds. I've just tried doing a release build with it excluded, and it built with no errors and is so far running just fine on my iPhone 6s.I'd be nice if React Native took the approach it took with
use_flipper!
in facebook/react-native@c72ecdb (see also our 61bda2a) towarduse_react_native!
. The "build configuration" (the thing we use at build time to say whether we're building for production or development) isn't known atpod install
time, which is the time the Podfile is run. So I don't see a way we could pass a correct value for theproduction
param thatuse_react_native!
expects.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this, it's possibly just fine to not do anything for now. Including
React-Core/DevSupport
in release builds is the status quo anyway.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha, yes, I guess I misread that code 🙃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree with all the above. This change is NFC -- we were always getting this pod, and we're still always getting it. And the appropriate thing would be for that function to do something like what
use_flipper!
does, and take a list of configurations for it to apply in.(Or else have some other way of being conditioned on the configuration.)