Skip to content

react-native 0.57.4 & gradle 4+ support#33

Open
patrickkempff wants to merge 7 commits intogodness84:masterfrom
patrickkempff:feature/rn-0.57.4-upgrade
Open

react-native 0.57.4 & gradle 4+ support#33
patrickkempff wants to merge 7 commits intogodness84:masterfrom
patrickkempff:feature/rn-0.57.4-upgrade

Conversation

@patrickkempff
Copy link

@patrickkempff patrickkempff commented Nov 2, 2018

  • Added method to customise dependency versions (by defining rootProject.ext), same implementation consistent with other react-native libraries like react-native-fast-image & react-native-maps
  • Fixed build issue on react-native 0.57.3
  • Upgraded android support recyclerview to 26.0.3 v27.1.1
  • Upgraded android buildtools to 26.0.3 v27.0.3
  • Fixed compiler warnings compile vs implementation more info
  • Removed unused NotAnimatedItemAnimator class
  • Upgraded to gradle plugin v3.1.4
  • Upgraded to gradle v4.4
  • Fixed the basic tests
  • Upgraded example app to react-native 0.57.4
  • Switched to yarn instead of npm for example app
  • Updated README.md to reflect new changes

"peerDependencies": {
"react": "^16.0.0-alpha.12",
"react-native": "^0.48.3"
"prop-types": "*",
Copy link
Owner

Choose a reason for hiding this comment

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

Why removing prop-types as dependency? Different packages can have different versions of prop-types, can't they?

Copy link
Author

Choose a reason for hiding this comment

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

I have added the prop-types as an peer dependency instead. As react-native is moving away from prop-types in favour of flow typings, I think we should investigate if we can ditch proptypes for flow/typescript typings.

Copy link
Owner

Choose a reason for hiding this comment

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

I don't like prop-types too, but adding it as a peer dependency means that users of this lib must have prop-types as a direct dependency in their main package.json, and I don't like it. Would you mind to leave it as a direct dependency of this lib? Afterwards, I'll merge this PR immediately!

Copy link
Author

Choose a reason for hiding this comment

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

@godness84 yeah of course! I will update it according to your feedback. 👍

@godness84
Copy link
Owner

@patrickkempff thank you for your great job! I added some suggestions, let me know what you think about

@patrickkempff
Copy link
Author

@godness84 I am a bit busy at the moment but I will take a look somewhere this week. Thank you for the feedback!

@enahum
Copy link

enahum commented Nov 9, 2018

@patrickkempff it would be awesome if you just apply the suggestions made by @godness84 so this can get merged, looking forward to it, I've included the PR in my fork.

On a different note, @godness84 would you take a PR that adds support to refresh the recycle list on both sides with a SwipeRefreshLayout ?

godness84 and others added 2 commits November 10, 2018 10:33
Co-Authored-By: patrickkempff <patrickkempff@gmail.com>
Co-Authored-By: patrickkempff <patrickkempff@gmail.com>
@patrickkempff
Copy link
Author

patrickkempff commented Nov 10, 2018

Thank you @godness84, I have applied your suggestions.

@ariona
Copy link

ariona commented Dec 5, 2018

when this will be merged?

@henrikra
Copy link

I came across this same problem when updating to RN 0.57.4. What if we make smaller PR which changes only this part:
image

Because all the other things are related to the example app. Only this one line change would make it work with RN 0.57.4. What do you guys think?

@patrickkempff
Copy link
Author

I created this PR a couple of months ago, if there is anything I can do to get this merged let me know.

@henrikra
Copy link

@patrickkempff Can you make smaller PR out of this? You could do PR which only does the changes in RecyclerViewBackedScrollViewManager.java file. That is enough for this to work with React Native 0.57.4. This way the PR is way smaller and easier to merge. After that has been merged then you can do other PR which updates the example app :)

@a396901990
Copy link

waiting this PR~

@Nishchit14
Copy link

OMG, This would be merged. It's blocking to upgrade RN to 0.57.

Is this library being maintained?

@henrikra
Copy link

Because this library is NOT maintained I have forked this library and made only the minimal changes in order to keep it running.
You can install my forked version with npm i react-native-recyclerview-fixed.
The repo for the fork is there https://github.com/henrikra/react-native-recyclerview-list

You can see from my PRs to my fork that I have made this library to work up to React Native 0.58.6 https://github.com/henrikra/react-native-recyclerview-list/pulls?q=is%3Apr+is%3Aclosed 🎉

@nastarfan
Copy link

nastarfan commented Nov 27, 2019

@henrikra Thanks for your repo, I manage to make it work on RN 0.59.10, debug version works perfectly.
However, I am facing an issue when trying to build release version of my app with command .\gradlew assembleRelease. I got the following error:

Note: there were 1 references to unknown classes.
      You should check your configuration for typos.
      (http://proguard.sourceforge.net/manual/troubleshooting.html#unknownclass)
Note: there were 875 unkept descriptor classes in kept class members.
      You should consider explicitly keeping the mentioned classes
      (using '-keep').
      (http://proguard.sourceforge.net/manual/troubleshooting.html#descriptorclass)
Note: there were 15 unresolved dynamic references to classes or interfaces.
      You should check if you need to specify additional program jars.
      (http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclass)
Warning: there were 8 unresolved references to program class members.
         Your input classes appear to be inconsistent.
         You may need to recompile the code.
         (http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedprogramclassmember)
Warning: Exception while processing task java.io.IOException: Please correct the above warnings first.
Thread(Tasks limiter_1): destruction

> Task :app:transformClassesAndResourcesWithProguardForRelease FAILED

FAILURE: Build failed with an exception.

I have confirmed that the issue is caused by this library, I've tried to remove it and build with no issue. I don't know if I suppose to report an issue on here since it doesn't seem to be actively maintained currently.
I hope you guys can help me if you know how to resolve this issue

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.

8 participants