-
Notifications
You must be signed in to change notification settings - Fork 138
[Shipping Labels Revamp] Update purchase screen with HAZMAT data #13847
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
Conversation
📲 You can test the changes from this Pull Request in WooCommerce-Wear Android by scanning the QR code below to install the corresponding build.
|
|
📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## trunk #13847 +/- ##
============================================
- Coverage 38.31% 38.29% -0.03%
Complexity 9357 9357
============================================
Files 2088 2089 +1
Lines 115379 115448 +69
Branches 14743 14769 +26
============================================
+ Hits 44206 44209 +3
- Misses 67147 67213 +66
Partials 4026 4026 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
… Purchase screen composable
|
@irfano @atorresveiga during this PR progress, I've noticed that the Purchased screen contains a code repetition of the Purchased composable. One of them is used solely for Preview purposes. This can be verified by comparing the code of the I understand the reasoning for the preview-only code, but this is causing a lot of confusion during development. More than once, I ran an entire Label purchase flow for tests and then noticed that I only updated the Preview composable, not the real one. I'm inclined to refactor this in a separate PR so that the |
Generated by 🚫 Danger |
| import androidx.compose.foundation.layout.Row | ||
| import androidx.compose.foundation.layout.fillMaxWidth | ||
| import androidx.compose.foundation.layout.padding | ||
| import androidx.compose.material.Icon |
Check warning
Code scanning / Android Lint
material and material3 are separate, incompatible design system libraries Warning
| import androidx.compose.foundation.layout.fillMaxWidth | ||
| import androidx.compose.foundation.layout.padding | ||
| import androidx.compose.material.Icon | ||
| import androidx.compose.material.MaterialTheme |
Check warning
Code scanning / Android Lint
material and material3 are separate, incompatible design system libraries Warning
| import androidx.compose.foundation.layout.padding | ||
| import androidx.compose.material.Icon | ||
| import androidx.compose.material.MaterialTheme | ||
| import androidx.compose.material.Surface |
Check warning
Code scanning / Android Lint
material and material3 are separate, incompatible design system libraries Warning
| import androidx.compose.material.Icon | ||
| import androidx.compose.material.MaterialTheme | ||
| import androidx.compose.material.Surface | ||
| import androidx.compose.material.Text |
Check warning
Code scanning / Android Lint
material and material3 are separate, incompatible design system libraries Warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I verified the Hazmat selection on the purchased screen. LGTM! 👍🏻
This makes sense, and we can do it in a separate PR. Opened an issue: WOOMOB-266 |
# Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/orders/wooshippinglabels/WooShippingLabelCreationScreen.kt # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/orders/wooshippinglabels/WooShippingLabelCreationViewModel.kt
df4e6cb to
b2944cf
Compare
Summary
Fix issue #13841 by updating the Purchased screen with the Hazmat data.
The Hazmat was already defined within the UI, but it wasn't carrying any data from the Creation form. To fix this, this PR updates the data wiring between the Creation form and Purchased screen to contain the selected Hazmat category.
Also, it updates the Hazmat card inside the Purchased screen to follow the Figma designs.
Screen Capture
Hazmat.purchased.screen.mp4
How to Test
Update release notes:
RELEASE-NOTES.txtif necessary.Reviewer (or Author, in the case of optional code reviews):
Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement: