Closed jarvislin closed 4 weeks ago
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20649-ffaf5de | |
Commit | ffaf5de2e15998e76d4f92055f97620789c35b7b | |
Direct Download | wordpress-prototype-build-pr20649-ffaf5de.apk |
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20649-ffaf5de | |
Commit | ffaf5de2e15998e76d4f92055f97620789c35b7b | |
Direct Download | jetpack-prototype-build-pr20649-ffaf5de.apk |
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Attention: Patch coverage is 48.57143%
with 18 lines
in your changes are missing coverage. Please review.
Project coverage is 40.46%. Comparing base (
0384227
) to head (ffaf5de
). Report is 9 commits behind head on trunk.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This pull request was deployed and Sentry observed the following issues:
org.wordpress.android.datasets.ReaderTagTable i...
View Issueorg.wordpress.android.datasets.ReaderPostTable ...
View IssueDid you find this useful? React with a 👍 or 👎
Refactor #20066
The previous implementation used a loop to make API requests to mark each note as read, this will be like DDoS if many users are marking their notes read at the same time. The new implementation only uses one API request to mark all notes as read.
To Test:
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):