Skip to content
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

React 16 #181

Merged
merged 1 commit into from
Jan 31, 2018
Merged

React 16 #181

merged 1 commit into from
Jan 31, 2018

Conversation

r0man
Copy link
Owner

@r0man r0man commented Dec 24, 2017

No description provided.

@r0man r0man force-pushed the react-16 branch 3 times, most recently from 9fddce7 to 0d92f6f Compare December 24, 2017 15:38
@DjebbZ
Copy link

DjebbZ commented Dec 28, 2017

Happy to see you started working on this !

I run the tests locally with lein ci, all passed (even in Nashorn and Phantom).

What can I do to help ? What remains to be done ?

@r0man
Copy link
Owner Author

r0man commented Dec 28, 2017

@DjebbZ This depends on an unreleased version of om.next (which is used for server rendering) and in the tests. I also disabled some rum tests, since there's also no version available for React 16 I think. Ideally, I would like to enable all those tests again before cutting a release. So basically I'm waiting for releases of om.next and rum.

@DjebbZ DjebbZ mentioned this pull request Dec 28, 2017
4 tasks
@DjebbZ
Copy link

DjebbZ commented Dec 28, 2017

I noticed the unreleased om.next, had to clone and build it locally.

I gave notice of your work in rum's repo, I think I'll try something tomorrow.

I don't see any change in your code regarding a syntax to handle React's fragments. See the discussion on reagent repo to find a common syntax for them.
Do you have a specific plan ?

@DjebbZ
Copy link

DjebbZ commented Jan 29, 2018

@tonsky has just released a new version of rum that supports React 16 tonsky/rum#151 (commits) v0.11.0
The only thing (I think) remaining for rum now is a Sablono version that supports React 16 fragment. At least you have a version of Rum to test.

@r0man r0man force-pushed the react-16 branch 2 times, most recently from 80d3a2f to 8e5f165 Compare January 29, 2018 20:12
@r0man
Copy link
Owner Author

r0man commented Jan 29, 2018

@DjebbZ I updated rum, enabled its tests again and merged your fragement branch. Everything looks good. I pushed 0.8.3-SNAPSHOT to Clojars for testing. I asked David for a release of om.next with the React 16 dependencies which will happen soon. Then all tests are passing again and I will cut a release. Thanks for the fragment support and pushing this through! :)

@DjebbZ
Copy link

DjebbZ commented Jan 30, 2018

👍

@r0man r0man merged commit b43321a into master Jan 31, 2018
@r0man r0man deleted the react-16 branch January 31, 2018 17:10
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.

None yet

2 participants