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
Added support of pull down to refresh feature for Android platform. #2787
Added support of pull down to refresh feature for Android platform. #2787
Conversation
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.
First, I love how "fast" react-native libraries/developers are when it comes to "bugs" that have existed in their libraries for years that are a huge deal breaker 😄.
Getting to the PR though; There are a couple of problems which are a "deal breaker" (imo).
When dealing with a public project or any project for that matter, ALWAYS conform to the code bases code style/practices.
This includes how they leave comments, indentation, ordering of methods (although it might be random, see next point), method/property naming and everything else inbetween.
You've mostly done this, although there are places where you've changed indentation (to the correct one technically, but see next point) and added spaces.
When dealing with a public project, always keep the PRs as small as possible. I can see you've "fixed" a lot of formatting "errors", but this just adds to more code to review. Keep it as simple as possible. If this was at a company I would be happy to see some code cleanup, but these developers are not paid and want to do the least possible 😓 . You've also moved around a couple of methods and in some cases duplicated them. Don't do unnecessary work!
android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
Outdated
Show resolved
Hide resolved
android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
Outdated
Show resolved
Hide resolved
android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
Outdated
Show resolved
Hide resolved
android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
Show resolved
Hide resolved
NOTE: if you have a modal with overflow, scroll down on said modal, release and then try to scroll up, it'll refresh instead of scrolling up. This is working as intended on iOS |
Hi @Kasea @muskan273, what do we need to do to get this merged in? Is the only issue the code style/formatting or is the modal with overflow a dealbreaker? |
@snaptravel-eng I think this also fixes pull to refresh on Android. It seems to be working on iOS only. |
Thanks. Yeah I understand the intention. How do we get this merged instead of stuck as a PR? |
does anyone know when this is getting merged? 👀 @muskan273 @Kasea @Titozzz @Saadnajmi |
@Kasea @jamonholmgren @Titozzz Can you please review the latest commit? I have made changes as suggested above. Let me know if I need to make any changes. |
Thanks for updating @muskan273 ! How do we get this merged instead of stuck as a PR? @Kasea @jamonholmgren @Titozzz |
|
I faced the same issue while implementing that feature. I have mentioned the solution in the below blog: |
@muskan273 Congrats on your first PR! |
is there anyone who can rebase master please i need this PR urgently. |
Is there any blocker for updating and merging this? The open bounty still applies: #2678 |
this pr doesn't work for loading web pages that have nested scroll views. The page i'm trying to load has a scrollable content block between a sticky header and footer. I can't scroll up within the scrollable content, it just triggers the refresh. Repro is to replace the example for Scrolling with this:
Recording of behavior: |
Hello 👋, this PR has been opened for more than 2 months with no activity on it. If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing! You have 7 days until this gets closed automatically |
Hi, I wanted to bring your attention back to a closed pull request that I believe requires further consideration. I have identified a solution for the issue discussed in this comment: #2787 (comment). Looking forward to your feedback and the possibility of reopening and resolving this pull request. |
No description provided.