-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2023-09-12] Design clean-up and consistency across expense
reports and requests.
#26138
Comments
Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new. |
@koko57 would you be up for this one? |
Sorry, I'll be ooo from tomorrow till 10th Sept., so maybe someone else from my team could take it? |
@mountiny @luacmartins can we get someone else on this one given the OOO? I think we really need to have these items cleaned up ahead of 6th September for the product promotions. |
asked here |
Also asked if any C+ has time to tackle this https://expensify.slack.com/archives/C02NK2DQWUX/p1693362407056109 I think Callstack might have a bit less availability now ahead of RNEU conference. |
Nice, thanks ya'll! |
Hi, I can work on this if no one from callstack has bandwidth |
@rushatgabhane Michael should be able to, you could do c+ role here to help with the code review |
Okay, so to be clear I'm just reviewing the PR that Michael will raise? |
Hi, I'm Michael (Mykhailo) from Callstack and I would like to work in this issue. |
@rezkiy37 let's do this! |
@JmillsExpensify, just to clarify the 4th step. The app already handles cases with one or multiple requests and receipts. I see only one discrepancy associated with the overlay, that counts the number of additional receipts. App/src/components/ReportActionItem/ReportPreview.js Lines 121 to 126 in 03d13f7
So, based on this investigation, I think we need to fix the overlay. Am I right? Please correct me if I am wrong 🙂 |
@mountiny, do you mean this case: Screen.Recording.2023-08-30.at.18.56.24.movShould we add a counter under the amount? |
@rezkiy37 Yes you're exactly right! Thank you for confirming. |
@rezkiy37 Yes correct, there should be the counter same as for the receipts or distance! |
@JmillsExpensify, is it possible to provide access for a design for this specific component? I am not sure, that I can do it precisely without colors, dimensions and so on. Thank you! ![]() |
I am actually not sure if we want that design |
ready for the payment |
I think we're just waiting on payment here |
@JmillsExpensify can you help with payment please? |
Bump @JmillsExpensify for payment |
Still waiting for payment? |
Still waiting for payment |
We only need to pay $500 to @situchan here, otherwise nothing to pay and we can close this. |
Offer sent to @situchan. |
Offer accepted and paid. |
We've been making a lot of fast-and-loose changes to requests and reports as part of waves3-wave5, and as a result of adding
merchant
names for wave4, the end result isn't what we intended. Accordingly, this is a summary of what's broken and needs to be fixed.We're showing right carets for all report and request previews, when instead right carets should be removed from all request and report previews.
Similarly,
IOU
reports are showing themerchant
when they should instead be showing thedescription
(because IOUs always have the same merchant, which isRequest
).expense
/ request preview, we only show the merchant.X requests
logic on report previews in the workspace chat. More specifically, when more than one request exists on theexpense
report, we replace themerchantName
withX requests
, where X is the number of requests on the report. We also show up to three receipt images in the report preview. If more than three receipts exist, then we show an overlay in the lower right corner of the right most receipt,+X
. This overlay counts the number of additional receipts (e.g. receipts over 3) that exist on the report but can't be seen. Examples for completeness.The text was updated successfully, but these errors were encountered: