Improve eReceipt visually in New Dot #55803

mkzie2 · 2025-01-27T17:37:14Z

Explanation of Change

Improve eReceipt visually in New Dot

Fixed Issues

Tests

Create card transaction
If we don't have card transactions, go to the transaction detail and add this command to the console (replace the ID after _ with the transactionID that we're viewing)

Onyx.merge(`transactions_8073227627479073933`, {
    amount: 1000,
    currency: 'USD',
    cardID: 4,
    merchant: 'United Airlines',
    mccGroup: 'Airlines',
    created: '2023-07-24 13:46:20',
    hasEReceipt: true,
});

or add this useEffect to MoneyRequestView

useEffect(() => {
    Onyx.merge(`transactions_${linkedTransactionID}`, {
        amount: 1000,
        currency: 'USD',
        cardID: 4,
        merchant: 'United Airlines',
        mccGroup: 'Goods',
        created: '2023-07-24 13:46:20',
        hasEReceipt: true,
    });
    
});

Notice the EReceipt preview and EReceipt detail
Verify that the UI is correct with the description here

Verify that no errors appear in the JS console

Offline tests

Same

QA Steps

Create card transaction
If we don't have card transactions, go to the transaction detail and add this command to the console

Onyx.merge(`transactions_8073227627479073933`, {
    amount: 1000,
    currency: 'USD',
    cardID: 4,
    merchant: 'United Airlines',
    mccGroup: 'Airlines',
    created: '2023-07-24 13:46:20',
    hasEReceipt: true,
});

or add this useEffect to MoneyRequestView

useEffect(() => {
    Onyx.merge(`transactions_${linkedTransactionID}`, {
        amount: 1000,
        currency: 'USD',
        cardID: 4,
        merchant: 'United Airlines',
        mccGroup: 'Goods',
        created: '2023-07-24 13:46:20',
        hasEReceipt: true,
    });
    
});

Notice the EReceipt preview and EReceipt detail
Verify that the UI is correct with the description here

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2025-02-03.at.16.17.38.mov

Android: mWeb Chrome

Screen.Recording.2025-02-03.at.15.08.30.mov

iOS: Native

Screen.Recording.2025-02-03.at.16.23.20.mov

iOS: mWeb Safari

Screen.Recording.2025-02-03.at.15.10.11.mov

MacOS: Chrome / Safari

Screen.Recording.2025-02-03.at.15.04.40.mov

MacOS: Desktop

Screen.Recording.2025-02-03.at.16.26.39.mov

melvin-bot · 2025-02-03T09:47:56Z

@shawnborton @ishpaul777 One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

shawnborton · 2025-02-03T20:15:04Z

It seems like the spacing is quite off from our mockups. Here is what I see in your videos:

Yet here is our Figma file:

Can you update and then we can review again from there?

ishpaul777 · 2025-02-03T20:38:40Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

ishpaul777 · 2025-02-03T21:06:54Z

@mkzie2 can you please provide steps to add a card transaction (maybe we need to mock it? if yes please provide code to execute to have the mocked transaction) Thank you!

dannymcclain · 2025-02-03T22:03:27Z

Aside from @shawnborton's comments, why does the receipt change colors between the preview and full receipt? I would assume it would stay the same between those views.

mkzie2 · 2025-02-04T05:05:40Z

Aside from @shawnborton's comments, why does the receipt change colors between the preview and full receipt? I would assume it would stay the same between those views.

No problem, this is because I hard-coded it to display the receipt.

mkzie2 · 2025-02-04T05:50:27Z

@shawnborton, I updated it to match the Figma. Please help to check again.

mkzie2 · 2025-02-04T05:50:45Z

can you please provide steps to add a card transaction (maybe we need to mock it? if yes please provide code to execute to have the mocked transaction) Thank you!

@ishpaul777 Updated the test step.

ishpaul777 · 2025-02-04T12:08:49Z

e-reciept	distance receipt

dont we want make distance e-receipt to follow similar design @Expensify/design @mkzie2

shawnborton · 2025-02-04T19:04:09Z

I think we should leave the map receipts alone for now. We can follow up later and change them a bit to match these new eReceipts, but I say we tackle eReceipts first so that we don't have too much scope creep in this particular issue.

shawnborton · 2025-02-04T19:07:54Z

It looks like the spacing is still off a bit. For example the content below the amount is too far to the left, we don't have enough inner padding. Please refer to the Figma file, but see this image as well:

src/components/EReceipt.tsx

mkzie2 · 2025-02-19T14:28:39Z

It's 160px on my side in the ad-hoc build

Screen.Recording.2025-02-19.at.21.28.05.mov

mkzie2 · 2025-02-19T14:30:18Z

And I'm still seeing all $0.00 and yellow receipts for the Reports page:

On it now, I think I know the problem now, it's because we're not using the snap shot data for EReceipt in search page then if this transaction doesn't exist in Onyx, it's display the default.

mkzie2 · 2025-02-19T14:48:38Z

And I'm still seeing all $0.00 and yellow receipts for the Reports page:

@shawnborton It's fixed now.

github-actions · 2025-02-20T00:57:39Z

🚧 @shawnborton has triggered a test build. You can view the workflow run here.

github-actions · 2025-02-20T01:23:23Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/55803/index.html	❌ FAILED ❌
	The QR code can't be generated, because the iOS build failed
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/55803/NewExpensify.dmg	https://55803.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

shawnborton · 2025-02-20T01:30:49Z

Definitely starting to feel better!

For receipt previews that are a bit wider, like this view here:

Why do we not have the same proportions where the receipt scales evenly? As in, notice how when you view the eReceipt itself, it doesn't have that much space around the outsides:

Also, why is it scrollable?

CleanShot.2025-02-19.at.20.30.03.mp4

Again, I feel like the best solution here is to treat the eReceipt like a big SVG, and just embed that SVG the same way we would embed a receipt image. Does that make sense?

dannymcclain · 2025-02-20T14:23:14Z

Totally agree with Shawn's comments.

mkzie2 · 2025-02-20T14:58:20Z

Again, I feel like the best solution here is to treat the eReceipt like a big SVG, and just embed that SVG the same way we would embed a receipt image. Does that make sense?

I think it's not an available solution in the front end.

cc @grgia Can we generate eReceipt image for card transaction in back-end? Is this is a possible idea?

shawnborton · 2025-02-21T14:38:13Z

Curious for your thoughts on this one @grgia when you get a minute, thanks!

shawnborton · 2025-02-24T14:35:27Z

I think it's not an available solution in the front end.

Why do you think it's not available on the front end? Basically instead of injecting all of this custom view/markup to create the eReceipt, you would do the same thing but using the SVG (xml) syntax. No idea if that would work on mobile though.

ishpaul777 · 2025-02-24T18:07:26Z

@shawnborton I believe it's not possible because we depend on React-native using their provided Components to handle the rendering content in the App. We can not switch to using other syntax as per my understanding.

maybe it would be possible to create a image link to receipt and push it from Backend like we do for per-diem receipt

shawnborton · 2025-02-24T18:37:51Z

Yeah, I can see that being a good option. Let's see if @grgia has an opinion on that one, or maybe we need to bring this to Slack for discussion.

ishpaul777 · 2025-02-24T18:43:55Z

@shawnborton If you can help me understand, whats your concern regarding rendering the receipt as is, is it because of the bugs, from rendering the receipt in a different places and sizes, or anything else?

shawnborton · 2025-02-24T18:52:27Z

Yeah, basically in all other cases, the receipt preview is just an image. This means that all we have to do is give the receipt a width of 100% and it will fill whatever thumbnail container we want it to fill, whether that's a tiny thumbnail from the reports page, or a larger thumbnail when viewing the expense view.

My concern here is that it feels like we need to rewrite eReceipt styles for every possible width that we might have, and it feels unsustainable and quite frankly a bit unpredictable. I would much rather just have a simple "image" of the eReceipt that can fill whatever space we need it to fill.

Does that make sense?

shawnborton · 2025-02-24T18:56:53Z

Basically this is the desired effect we want for eReceipts - it will just fill whatever container it is in. The same exact way we handle receipt images:

CleanShot.2025-02-24.at.13.56.01.mp4

ishpaul777 · 2025-02-24T19:19:04Z

i agree with your point of having the component work flawlessly no matter where it it used 👍 , i think @mkzie2 has wrote some code logic to scale the the receipt according to the parent container width it just does not work properly, @mkzie2 do you think you would be able to refine the logic make the component work flawlessly as shown in video ^ or should we be exploring other solutions, Thank you for your hard work so far!

mkzie2 · 2025-02-25T17:50:34Z

I will investigate this solution again and give an update tomorrow

mkzie2 · 2025-02-26T19:07:49Z

@shawnborton, please help check if it's the correct result.

result-1.mov

shawnborton · 2025-02-26T19:17:35Z

That does seem better, let's fire up a test build and take it for a spin!

github-actions · 2025-02-26T19:18:07Z

🚧 @shawnborton has triggered a test hybrid app build. You can view the workflow run here.

github-actions · 2025-02-26T19:43:44Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/55803/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/55803/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/55803/NewExpensify.dmg	https://55803.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

shawnborton · 2025-02-26T20:08:25Z

Hmm that's an improvement but it's still not technically working exactly as I was showing above. It's not truly scaling at it's exact proportions depending on the outer container width. What can we do about that?

Also, on the reports page, most of the eReceipts are yellow and don't have an icon:

CleanShot.2025-02-26.at.15.07.29.mp4

What's going on there? Because then when I open up the receipt, it shows the icon and it's even a different color.

mkzie2 added 8 commits January 14, 2025 23:34

add test branch

e076d99

resolve conflict

6f5000a

use only one background

0f3ff8f

Merge branch 'main' into mkzie2-issue/55083

cc254f6

fix ui in native

28ce4b8

update story

fb3b2fb

fix lint error

c29d6da

remove default value

7bb31bb

mkzie2 marked this pull request as ready for review February 3, 2025 09:47

mkzie2 requested review from a team as code owners February 3, 2025 09:47

melvin-bot bot requested review from ishpaul777 and shawnborton and removed request for a team February 3, 2025 09:47

mkzie2 mentioned this pull request Feb 3, 2025

[$250] Improve eReceipt visually in New Dot #55083

Open

Merge branch 'main' into mkzie2-issue/55083

f7903f2

mkzie2 added 2 commits February 4, 2025 12:32

update ereceipt style

b60b1fb

update background image style

6fec798

ishpaul777 reviewed Feb 5, 2025

View reviewed changes

src/components/EReceipt.tsx Outdated Show resolved Hide resolved

update ERecipt in search using the transaction data from snapshot

1be46df

Merge branch 'main' into mkzie2-issue/55083

1405ef9

mkzie2 added 2 commits February 24, 2025 14:48

Merge branch 'main' into mkzie2-issue/55083

bd3a4a0

fix the receipt is scrollable

f990808

mkzie2 added 4 commits February 26, 2025 23:31

Merge branch 'main' into mkzie2-issue/55083

549c582

fix EReceipt preview style

a28e965

fix native style

db16a66

fix prettier

e683dcc

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Improve eReceipt visually in New Dot #55803

Improve eReceipt visually in New Dot #55803

mkzie2 commented Jan 27, 2025 •

edited

Loading

melvin-bot bot commented Feb 3, 2025

shawnborton commented Feb 3, 2025

ishpaul777 commented Feb 3, 2025

ishpaul777 commented Feb 3, 2025 •

edited

Loading

dannymcclain commented Feb 3, 2025

mkzie2 commented Feb 4, 2025

mkzie2 commented Feb 4, 2025

mkzie2 commented Feb 4, 2025

ishpaul777 commented Feb 4, 2025 •

edited

Loading

shawnborton commented Feb 4, 2025

shawnborton commented Feb 4, 2025

mkzie2 commented Feb 19, 2025

mkzie2 commented Feb 19, 2025

mkzie2 commented Feb 19, 2025

github-actions bot commented Feb 20, 2025

github-actions bot commented Feb 20, 2025

shawnborton commented Feb 20, 2025

dannymcclain commented Feb 20, 2025

mkzie2 commented Feb 20, 2025

shawnborton commented Feb 21, 2025

shawnborton commented Feb 24, 2025

ishpaul777 commented Feb 24, 2025 •

edited

Loading

shawnborton commented Feb 24, 2025

ishpaul777 commented Feb 24, 2025

shawnborton commented Feb 24, 2025

shawnborton commented Feb 24, 2025

ishpaul777 commented Feb 24, 2025

mkzie2 commented Feb 25, 2025

mkzie2 commented Feb 26, 2025

shawnborton commented Feb 26, 2025

github-actions bot commented Feb 26, 2025

github-actions bot commented Feb 26, 2025

shawnborton commented Feb 26, 2025

Improve eReceipt visually in New Dot #55803

Are you sure you want to change the base?

Improve eReceipt visually in New Dot #55803

Conversation

mkzie2 commented Jan 27, 2025 • edited Loading

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Feb 3, 2025

shawnborton commented Feb 3, 2025

ishpaul777 commented Feb 3, 2025

Reviewer Checklist

Screenshots/Videos

ishpaul777 commented Feb 3, 2025 • edited Loading

dannymcclain commented Feb 3, 2025

mkzie2 commented Feb 4, 2025

mkzie2 commented Feb 4, 2025

mkzie2 commented Feb 4, 2025

ishpaul777 commented Feb 4, 2025 • edited Loading

shawnborton commented Feb 4, 2025

shawnborton commented Feb 4, 2025

mkzie2 commented Feb 19, 2025

mkzie2 commented Feb 19, 2025

mkzie2 commented Feb 19, 2025

github-actions bot commented Feb 20, 2025

github-actions bot commented Feb 20, 2025

shawnborton commented Feb 20, 2025

dannymcclain commented Feb 20, 2025

mkzie2 commented Feb 20, 2025

shawnborton commented Feb 21, 2025

shawnborton commented Feb 24, 2025

ishpaul777 commented Feb 24, 2025 • edited Loading

shawnborton commented Feb 24, 2025

ishpaul777 commented Feb 24, 2025

shawnborton commented Feb 24, 2025

shawnborton commented Feb 24, 2025

ishpaul777 commented Feb 24, 2025

mkzie2 commented Feb 25, 2025

mkzie2 commented Feb 26, 2025

shawnborton commented Feb 26, 2025

github-actions bot commented Feb 26, 2025

github-actions bot commented Feb 26, 2025

shawnborton commented Feb 26, 2025

mkzie2 commented Jan 27, 2025 •

edited

Loading

ishpaul777 commented Feb 3, 2025 •

edited

Loading

ishpaul777 commented Feb 4, 2025 •

edited

Loading

ishpaul777 commented Feb 24, 2025 •

edited

Loading