-
-
Notifications
You must be signed in to change notification settings - Fork 412
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
Update repo and example to React Native 0.73 #879
Update repo and example to React Native 0.73 #879
Conversation
The second lock file (example/yarn.lock) can be removed if we update to yarn 4 and use yarn workspaces. Yarn 1 workspaces requires the root package to be private, which doesn't work for our case. Would there be interest in upgrading? I can make a PR if so. |
hello @Saadnajmi and thank you for the PR! I just want to make sure of one thing - I want to be able to run the example app, and have hot reloading working when I make edits in the Thank you |
Hey, sure I'll check that out. It seems I have a couple of things to check out, as the CI is failing.
|
Hello, With rnx kit, can you point me to some docs around what specifically the things you added (metro config it seems?) do? I haven't used that before so unless there's some really good benefits I would probably prefer to not have it so that me or anyone else doesn't need to understand one more thing to contribute. TY. Luckily the CI is fairly solid in this package so I trust that when it's green everything works. |
dabffe1
to
771fc59
Compare
@Saadnajmi this will be a shot in the dark, but would perhaps MSFT be interested in sponsoring the maintenance of the module? |
@vonovak Sorry, I asked around a bit, and I don't think we're at a point where we can sponsor repos at this time 🙁. Meanwhile, I'm happy to spend time submitting PRs to fix issues / do some maintenance as they come up for stuff we care about (currently, that's adding visionOS support to several repos). Speaking of, I do hope the extra changes help with the maintenance, since adding visionOS support was really just a one line change but I figured it's worth trying to make the world better while we're at it 🙂 . For the windows development / maintenance, feel free to ping me or other Microsoft people and I can redirect to someone who does RN Windows dev (not me because I only really do Apple 😀 ). For this PR, I need to keep working on making the CI green. You can probably ignore till that's done and/or I ping you about it, does that work? |
Hey, thank you for the comment, works for me! 🙂 👍 |
EDIT: I ended up just incorporating @shwanton 's fix into this PR so that works! Hey @vonovak I think I've fixed most of the issues, and the remaining one is that iOS is failing to build with the new architecture on 0.73 (which this PR updates the example app to). I see that @shwanton has a separate PR for that fix (#878) so I'll try and coordinate with him how we handle that. Two main questions:
|
Yes, feel free to split the PR up 🙂. As for codegen-generated code, if you find that the currently generated code is the same as the one we have checked-in in the repo, then I guess there's no need to have it checked in. But I find it unlikely. There were some customizations made on it, I don't remember exactly what it was, maybe some intricacies related to layout or state as you're saying. |
@shwanton and I chatted offline about it. The repo adds custom state to the shadow note to track the date pickers' frame. That can't be replicated with just codegen atm afaik, so it needs to stay checked in. I may be wrong |
Just got this message from circle: In the last 30 days your team used the Free plan to test, build, and deploy for approximately 8752 minutes a day. That's a lot of building. Without additional credits, your team will not be able to continue until the next refill on 05/22/24. -- So in case building doesn't eun this might be the reason. |
Ah, seems I have been going a bit too hard 😅 I can batch my updates better then. That does mean I probably won't revisit till 5/22/24. |
^ This is the 1st commit message: Update RNTA to 0.73 ^ The commit message react-native-datetimepicker#2 will be skipped: ^ update RNTA
Co-authored-by: Vojtech Novak <vonovak@gmail.com>
Co-authored-by: Vojtech Novak <vonovak@gmail.com>
Co-authored-by: Vojtech Novak <vonovak@gmail.com>
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.
🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀
🎉 This issue has been resolved in version 8.0.0 🎉 If this package helps you, consider sponsoring us! 🚀 |
Updating our rnx-kit preset :) |
Summary
Update the library and example app in this repo to React Native 0.73, which allows us to add a visionOS example app. As of #888 , dateTimePicker now has a minimum React Native version of 0.73. This PR will update the rest of the repo to reflect that.
To do this, I did:
react-native-test-app
used to the latest major releaseTest Plan
visionOS test app boots:
iOS test app for me boots as well. I didn't test Android or Windows.
What's required for testing (prerequisites)?
Xcode 15.2
What are the steps to reproduce (after prerequisites)?
Just run
pod install
and run the visionOS test app as you would an iOS test appCompatibility
Checklist
README.md
example/App.js
)