Skip to content

Use data client for peer review calls #2937

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 3 commits into from
Jun 7, 2019

Conversation

maskaravivek
Copy link
Member

@maskaravivek maskaravivek commented May 6, 2019

Fixes #2921

This is the first PR where we start leveraging the data client library.

The APIs were not defined in the library so as defined in the documentation, I have created a ReviewInterface for the API calls.

Check out the documentation to go through the steps.

https://github.com/wikimedia/wikimedia-android-data-client

@maskaravivek maskaravivek marked this pull request as ready for review June 5, 2019 08:57
Copy link

@pullrequest pullrequest bot left a comment

Choose a reason for hiding this comment

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

✅ A review job has been created and sent to the PullRequest network.


@maskaravivek you can click here to see the review status or cancel the code review job.

@codecov-io
Copy link

codecov-io commented Jun 5, 2019

Codecov Report

Merging #2937 into master will increase coverage by 0.01%.
The diff coverage is 73.68%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master   #2937      +/-   ##
=========================================
+ Coverage    3.69%    3.7%   +0.01%     
=========================================
  Files         249     249              
  Lines       12271   12226      -45     
  Branches     1091    1085       -6     
=========================================
  Hits          453     453              
+ Misses      11783   11739      -44     
+ Partials       35      34       -1
Impacted Files Coverage Δ
...fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.java 1.05% <ø> (+0.21%) ⬆️
.../free/nrw/commons/di/CommonsApplicationModule.java 0% <ø> (ø) ⬆️
.../java/fr/free/nrw/commons/di/NetworkingModule.java 0% <0%> (ø) ⬆️
...ava/fr/free/nrw/commons/review/ReviewActivity.java 0% <0%> (ø) ⬆️
.../java/fr/free/nrw/commons/review/ReviewHelper.java 88.88% <87.5%> (+2.4%) ⬆️

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 06dbfef...1e62e8c. Read the comment docs.

Copy link
Collaborator

@neslihanturan neslihanturan left a comment

Choose a reason for hiding this comment

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

Thanks @maskaravivek

@neslihanturan neslihanturan merged commit 6f9d69e into commons-app:master Jun 7, 2019
@misaochan
Copy link
Member

@neslihanturan , what manual tests did you perform with this?

@neslihanturan
Copy link
Collaborator

Hi @misaochan , since this looked like a basic refactor and all tests are included I played around peer review such as marking images as mis-categorized etc. But I can't say precise test steps, will definitely write next time. Now I remake a test too on master since this code is already on master (on beta cluster API 26 emulator), and mis-categorized thing works but others has no effect. Did you also experience this issue?

@maskaravivek
Copy link
Member Author

Hi @misaochan , since this looked like a basic refactor and all tests are included I played around peer review such as marking images as mis-categorized etc. But I can't say precise test steps, will definitely write next time. Now I remake a test too on master since this code is already on master (on beta cluster API 26 emulator), and mis-categorized thing works but others has no effect. Did you also experience this issue?

Did something break?

@neslihanturan
Copy link
Collaborator

yes @maskaravivek according to my beta cluster tests current master review questions has no effect except category one.

@misaochan
Copy link
Member

Yes, same issue here. I think for PRs related to our backend overhaul, we need to manually test them a bit more rigorously than we would other PRs, due to the high potential for side effects.

@neslihanturan
Copy link
Collaborator

I agree, will be more careful next time. Do you think we should revert this merge?

@maskaravivek
Copy link
Member Author

I agree, will be more careful next time. Do you think we should revert this merge?

It would be great if we could keep the changes in master as my other changes are based on it. I can pick up the fixes for the issues immediately.

@neslihanturan
Copy link
Collaborator

Okay, thanks @maskaravivek !

@misaochan
Copy link
Member

Sure, we can keep the changes in master, just link to this when you have your fix PR up.

@maskaravivek
Copy link
Member Author

Sure, we can keep the changes in master, just link to this when you have your fix PR up.

Sure. :)

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.

Optimize peer review, avoid unnecessary calls
4 participants