Closed irfano closed 4 weeks ago
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20656-8fddc15 | |
Commit | 8fddc153cf8ad278850a211d324768ba24258e82 | |
Direct Download | wordpress-prototype-build-pr20656-8fddc15.apk |
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20656-8fddc15 | |
Commit | 8fddc153cf8ad278850a211d324768ba24258e82 | |
Direct Download | jetpack-prototype-build-pr20656-8fddc15.apk |
Attention: Patch coverage is 87.50000%
with 1 lines
in your changes are missing coverage. Please review.
Project coverage is 40.47%. Comparing base (
3f7287b
) to head (8fddc15
). Report is 27 commits behind head on trunk.
Files | Patch % | Lines |
---|---|---|
...rg/wordpress/android/util/text/PercentFormatter.kt | 85.71% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Fixes #17447
When the device language is set to Arabic, numbers with the percentage were being displayed as "%96-". This was the output of
android.icu.text.NumberFormat
function. I couldn't find any documentation related to this issue, but usingjava.text.NumberFormat
resolves it. See the screenshot below:Ignore the inaccurate chart. I manipulated the code to display the negative percentage.
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)
PercentFormatterTest
.PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):