Closed aditi-bhatia closed 3 weeks ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20524-2d30d0b | |
Commit | 2d30d0b8f44ec4ad724ed8bc5efe52f42ea168e3 | |
Direct Download | jetpack-prototype-build-pr20524-2d30d0b.apk |
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20524-2d30d0b | |
Commit | 2d30d0b8f44ec4ad724ed8bc5efe52f42ea168e3 | |
Direct Download | wordpress-prototype-build-pr20524-2d30d0b.apk |
Attention: Patch coverage is 0%
with 14 lines
in your changes are missing coverage. Please review.
Project coverage is 40.43%. Comparing base (
27ad674
) to head (2d30d0b
). Report is 484 commits behind head on trunk.
Files | Patch % | Lines |
---|---|---|
...rdpress/android/ui/stats/refresh/StatsViewModel.kt | 0.00% | 14 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
1 Warning | |
---|---|
:warning: | PR is not assigned to a milestone. |
Generated by :no_entry_sign: Danger
Fixes https://github.com/wordpress-mobile/WordPress-Android/issues/20397
This PR fixes an issue where pull to refresh wouldn't update Stats. This was happening because
statsSection
was being set toTRAFFIC
with no information on time granularity. This PR mapsStatsGranularity
to its correspondingStatsSection
so that we can refresh the correctuseCase
. For example, it mapsStatsGranularity.DAYS
toStatsSection.DAYS
so the correct data can be refreshed. Alternatively, we could choose to refreshall
granularities on pull to refresh which would remove the need for mapping with the feature flag on, but would also be less efficient.To Test:
With the Stats feature flag on, navigate to the Stats page.
Turn data off and change the granularity or time period.
You should see
There was a problem loading your data, refresh your page to try again
:Turn data on again. Refresh the page and it should display data.
Repeat steps 1-4 with the feature flag off.
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):