Format message for olddot action #45683

hungvu193 · 2024-07-18T14:56:42Z

Details

Update the header title of report integration message action thread.

Fixed Issues

Tests

Prerequisite: User has a failed report export, following #44170 (comment) or the reproduce video in the linked issue steps.

Go to a report that has failed export message.
Hover on it, click on reply in thread.
Verify that the thread title is the same with its parent.

Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

Same as Tests.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Uploading Screen Recording 2024-07-19 at 00.41.11.mov…

Screen.Recording.2024-07-19.at.00.43.18.mov

Android: mWeb Chrome

Screen.Recording.2024-07-19.at.00.34.27.mov

iOS: Native

Screen.Recording.2024-07-19.at.00.32.26.mov

iOS: mWeb Safari

Screen.Recording.2024-07-18.at.23.26.31.mov

MacOS: Chrome / Safari

Screen.Recording.2024-07-18.at.23.08.04.mov

MacOS: Desktop

Screen.Recording.2024-07-18.at.23.24.09.mov

melvin-bot · 2024-07-18T16:25:30Z

@fedirjh Please 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]

hungvu193 · 2024-07-18T16:28:02Z

Not related to this PR but I'm seeing You when open the thread with EXPORTINTEGRATION reportAction, I'm not sure if it's correct.

Screen.Recording.2024-07-18.at.23.27.12.mov

fedirjh · 2024-07-18T19:52:53Z

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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.js 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.
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

CleanShot.2024-07-18.at.20.50.41.mp4

MacOS: Desktop

CleanShot.2024-07-18.at.21.13.02.mp4

fedirjh

Looks good

arosiclair · 2024-07-19T12:50:03Z

Not related to this PR but I'm seeing You when open the thread with EXPORTINTEGRATION reportAction, I'm not sure if it's correct.

Would that be fixed by using getExportIntegrationLastMessageText in this same function? If so can we clean that up in this PR too?

hungvu193 · 2024-07-19T16:18:55Z

@arosiclair Sure. I have a question, as commented here, EXPORTED_TO_INTEGRATION is also oldDot reportAction right?

App/src/CONST.ts

Line 691 in 567627d

EXPORTED_TO_INTEGRATION: 'EXPORTINTEGRATION', // OldDot Action

If so we can add EXPORTED_TO_INTEGRATION to isOldDotReportAction 's array, and the following case into our getMessageOfOldDotReportAction:

        case CONST.REPORT.ACTIONS.TYPE.EXPORTED_TO_INTEGRATION:
            return getExportIntegrationLastMessageText(oldDotAction as ReportAction);

Then we can also removed this condition since getMessageOfOldDotReportAction already covered this case:

App/src/libs/OptionsListUtils.ts

Lines 740 to 742 in 567627d

    
           } else if (lastReportAction?.actionName === 'EXPORTINTEGRATION') { 
        
               lastMessageTextFromReport = ReportActionUtils.getExportIntegrationLastMessageText(lastReportAction); 
        
           } else if (lastReportAction?.actionName && ReportActionUtils.isOldDotReportAction(lastReportAction)) {

arosiclair · 2024-07-19T19:07:13Z

@arosiclair Sure. I have a question, as commented here, EXPORTED_TO_INTEGRATION is also oldDot reportAction right?

It's not actually since it needs special formatting to handle its links and pending states.

src/libs/ReportActionsUtils.ts

hungvu193 · 2024-07-21T03:26:28Z

Thanks. I've updated the code.

OSBotify · 2024-07-22T13:16:36Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-07-23T08:36:50Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.11-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-24T00:17:08Z

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 9.0.11-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-25T03:17:09Z

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.11-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-26T05:14:52Z

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.12-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

hungvu193 added 4 commits July 18, 2024 21:50

format message for integration action

3de0f40

fix lint

85b62d8

update report name for all oldDot action

9aaad03

remove reduntdant code

09d71bc

hungvu193 marked this pull request as ready for review July 18, 2024 16:25

hungvu193 requested a review from a team as a code owner July 18, 2024 16:25

melvin-bot bot removed the request for review from a team July 18, 2024 16:25

melvin-bot bot requested a review from fedirjh July 18, 2024 16:25

hungvu193 changed the title ~~Format message for integration action~~ Format message for olddot action Jul 18, 2024

This comment was marked as outdated.

Sign in to view

fedirjh approved these changes Jul 18, 2024

View reviewed changes

melvin-bot bot requested a review from arosiclair July 18, 2024 20:14

polish export_to_integration message

cd979db

arosiclair requested changes Jul 19, 2024

View reviewed changes

src/libs/ReportActionsUtils.ts Outdated Show resolved Hide resolved

hungvu193 added 2 commits July 21, 2024 10:18

update export to integration format message

6fab342

resolve conflict

5a22379

hungvu193 requested a review from arosiclair July 21, 2024 03:26

arosiclair approved these changes Jul 22, 2024

View reviewed changes

arosiclair merged commit bd8c58b into Expensify:main Jul 22, 2024
14 checks passed

github-actions bot mentioned this pull request Jul 23, 2024

Deploy Checklist: New Expensify 2024-07-23 #45991

Closed

95 tasks

melvin-bot bot mentioned this pull request Jul 25, 2024

[HOLD for payment 2024-08-01] [$250] Xero export - Different thread title when opening export error message in thread #45669

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Format message for olddot action #45683

Format message for olddot action #45683

hungvu193 commented Jul 18, 2024 •

edited

Loading

melvin-bot bot commented Jul 18, 2024

hungvu193 commented Jul 18, 2024

This comment was marked as outdated.

fedirjh commented Jul 18, 2024 •

edited

Loading

fedirjh left a comment

arosiclair commented Jul 19, 2024

hungvu193 commented Jul 19, 2024

arosiclair commented Jul 19, 2024

hungvu193 commented Jul 21, 2024

OSBotify commented Jul 22, 2024

OSBotify commented Jul 23, 2024

OSBotify commented Jul 24, 2024

OSBotify commented Jul 25, 2024

OSBotify commented Jul 26, 2024

Format message for olddot action #45683

Format message for olddot action #45683

Conversation

hungvu193 commented Jul 18, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jul 18, 2024

hungvu193 commented Jul 18, 2024

This comment was marked as outdated.

fedirjh commented Jul 18, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

fedirjh left a comment

Choose a reason for hiding this comment

arosiclair commented Jul 19, 2024

hungvu193 commented Jul 19, 2024

arosiclair commented Jul 19, 2024

hungvu193 commented Jul 21, 2024

OSBotify commented Jul 22, 2024

OSBotify commented Jul 23, 2024

OSBotify commented Jul 24, 2024

OSBotify commented Jul 25, 2024

OSBotify commented Jul 26, 2024

hungvu193 commented Jul 18, 2024 •

edited

Loading

fedirjh commented Jul 18, 2024 •

edited

Loading