Skip to content

Fix issue #1332 : Contribution Image auto/manual refresh if fetching fails #1375

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

Merged
merged 1 commit into from
Apr 30, 2018

Conversation

devaar100
Copy link
Contributor

Description

Fixes #1332
Addition of a swipe refresh layout to enable manual refresh

Tests performed

Tested on Android version 6.0.1

@devaar100 devaar100 changed the base branch from master to 2.7.x-release March 27, 2018 06:21
@neslihanturan
Copy link
Collaborator

As we talked on issue, we prefer auto refresh, not manual swipe refresh. Let ask @misaochan if this is suitable?

@misaochan
Copy link
Member

I think adding swipe refresh as a backup could be a good idea, especially if people don't want to wait for an auto-refresh. When I tested real-time movement recently in a car, I could move out of the range of the Nearby pins without an auto-refresh happening.

@misaochan
Copy link
Member

Oh wait, sorry, this is for contributions? Swipe refresh should be OK for that too. I would be against adding a refresh button though.

@neslihanturan
Copy link
Collaborator

neslihanturan commented Apr 16, 2018

I still don't understand why we would need a swipe refresh while we have already auto refresh. Besides, this breaks tests :(

But if everyone agrees, then we should add it to our codebase. @devaar100 would you like to investigate why tests fails?

@neslihanturan neslihanturan changed the title Fix issue #1332 Fix issue #1332 : Contribution Image auto/manual refresh if fetching fails Apr 16, 2018
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (2.7.x-release@1bede8f). Click here to learn what that means.
The diff coverage is 0%.

Impacted file tree graph

@@               Coverage Diff               @@
##             2.7.x-release   #1375   +/-   ##
===============================================
  Coverage                 ?   3.28%           
===============================================
  Files                    ?     128           
  Lines                    ?    6877           
  Branches                 ?     674           
===============================================
  Hits                     ?     226           
  Misses                   ?    6636           
  Partials                 ?      15
Impacted Files Coverage Δ
...w/commons/contributions/ContributionsActivity.java 0% <ø> (ø)
...mmons/contributions/ContributionsListFragment.java 0% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1bede8f...27a8ce9. Read the comment docs.

@neslihanturan
Copy link
Collaborator

Thanks @devaar100 it worked for me

@neslihanturan neslihanturan merged commit 5aba745 into commons-app:2.7.x-release Apr 30, 2018
@misaochan
Copy link
Member

It seems that this has been merged into the wrong branch - it should have gone to master instead of 2.7.x-release. I apologize but I will have to revert this, as we need to do an urgent hotfix to production for #1599 that will bypass beta testing, and this PR cannot be included in it.

I will revert this from the 2.7.x-release branch, but it should still exist in master because I have updated master with that branch. Please let me know if there are issues with it.

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.

4 participants