-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
feat: 4674 - added the "other photos" section #4866
feat: 4674 - added the "other photos" section #4866
Conversation
New files: * `product_image_gallery_other_view.dart`: Display of the other pictures of a product. * `product_image_other_page.dart`: Full page display of a raw product image. Impacted file: * `product_image_gallery_view.dart`: added the "other photos" section; fixed a "refresh not working" bug
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #4866 +/- ##
==========================================
- Coverage 9.77% 9.72% -0.05%
==========================================
Files 313 315 +2
Lines 15976 16044 +68
==========================================
Hits 1561 1561
- Misses 14415 14483 +68 ☔ View full report in Codecov by Sentry. |
Generally speaking, would displaying the main 4 pictures, then a "more photos" button that downloads then displays the "other" pics do the trick? |
Yes, at this point 👍 |
@teolemon Coded and pushed: the first time the user goes to that page we display a button instead of the whole list of photos. |
There could be a confusion with a photo button taking button. Let's rephrase the button to "View all existing photos for this product" |
Impacted files: * `app_en.arb`: add new label for "click for other photo" button * `app_fr.arb`: add new label for "click for other photo" button * `product_image_gallery_view.dart`: used new label for "click for other photo" button
@teolemon Coded and pushed: |
I'm not a big fan of this button. We need to keep a hierarchy and not mix different things. |
@g123k In those cases, please approve the PR first and then I'll do the minor changes. With just a couple of reviewers at the moment, we need to remove frictions in the PR approval process in order to have smoother code integration. Assuming that smoother code integration is a good idea. |
final AppLocalizations appLocalizations = AppLocalizations.of(context); | ||
final double screenWidth = MediaQuery.of(context).size.width; | ||
final double squareSize = screenWidth / _columns; | ||
return FutureBuilder<List<int>>( |
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.
Oh no, please don't use a FutureBuilder
, that's the shittiest Widget ever.
A separated class with a ValueNotifier
-like thing or I don't know which state management solution, but never mix UI with how the data is fetched.
I know the app uses this pattern everywhere, but if I can stop the spreading of this 🦠, I prefer.
Edit: If you don't see what I mean, I can eventually edit your PR
|
@teolemon The |
Thank you guys for your comments and reviews! |
What
Screenshot
Part of
Files
New files:
product_image_gallery_other_view.dart
: Display of the other pictures of a product.product_image_other_page.dart
: Full page display of a raw product image.Impacted file:
product_image_gallery_view.dart
: added the "other photos" section; fixed a "refresh not working" bug