Skip to content

Conversation

@tido64
Copy link
Member

@tido64 tido64 commented Oct 22, 2020

Summary:

Bump the example app to 0.62.

We only bump to 0.62 because react-native-macos 0.63 isn't out yet. To simplify our lives, we stay in sync to avoid any potential issues from having both 0.62 and 0.63 installed.

Test Plan:

The test app must build and boot on the following platforms:

@tido64 tido64 force-pushed the tido/fixup-old-refs branch from afdb129 to 816a7f4 Compare October 22, 2020 21:57
Base automatically changed from tido/fixup-old-refs to master October 22, 2020 22:26
@tido64 tido64 force-pushed the tido/bump-rn-62 branch 3 times, most recently from 7ee0ae5 to 0fbc2df Compare October 22, 2020 23:50
@tido64 tido64 marked this pull request as ready for review October 24, 2020 06:43
Copy link
Member

@krizzu krizzu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic work 🎉 I'm glad for react-native-test-app integration!

Let's address web in follow up PR, like you proposed. I have an idea how to fix it.

Also, I know what happened to the formatting - upgrading to latest community eslint config. That version includes Prettier 2.0.2 dependency, which included a change that generates a lot of churn in codebases, without an option to disable.

I think it's ugly, but nothing we can here. We can, however, disable adding brackets in arrow functions - could you add another entry to .prettierrc? 🙏

+  "arrowParens": "avoid"

@tido64
Copy link
Member Author

tido64 commented Oct 24, 2020

Fantastic work 🎉 I'm glad for react-native-test-app integration!

It's only integrated for macOS example app. I'll try to migrate the other platforms as well.

I think it's ugly, but nothing we can here. We can, however, disable adding brackets in arrow functions - could you add another entry to .prettierrc? 🙏

I'd rather not have a .prettierrc to be honest. I kind of agree with this formatting. Makes it consistent for any number of arguments, e.g.:

const single = (value) => value;
const pair = (x, y) => [x, y];

The whole point of Prettier is to avoid these discussions. I think we should use the defaults.

We only bump to 0.62 because react-native-macos 0.63 isn't out yet. To
simplify our lives, we stay in sync to avoid any potential issues from
having both 0.62 and 0.63 installed.
@krizzu
Copy link
Member

krizzu commented Oct 24, 2020

Let's go with the defaults then, like you suggested.

@tido64 tido64 merged commit 970eaa5 into master Oct 24, 2020
@tido64 tido64 deleted the tido/bump-rn-62 branch October 24, 2020 13:06
krizzu pushed a commit that referenced this pull request Oct 24, 2020
* chore: Bump RN to 0.62

We only bump to 0.62 because react-native-macos 0.63 isn't out yet. To
simplify our lives, we stay in sync to avoid any potential issues from
having both 0.62 and 0.63 installed.

* chore(Windows): Remove workaround causing crash on 0.62
krizzu pushed a commit that referenced this pull request Oct 24, 2020
* chore: Bump RN to 0.62

We only bump to 0.62 because react-native-macos 0.63 isn't out yet. To
simplify our lives, we stay in sync to avoid any potential issues from
having both 0.62 and 0.63 installed.

* chore(Windows): Remove workaround causing crash on 0.62
@krizzu
Copy link
Member

krizzu commented Nov 2, 2020

🎉 This PR is included in version 1.13.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@krizzu krizzu added the released label Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants