[No QA] refactor getReportName to have 1 param#83177
Conversation
Codecov Report✅ Changes either increased or maintained existing code coverage, great job!
|
|
@DylanDylann 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] |
|
|
||
| const reportID = report?.reportID; | ||
| const currentChatName = getReportName(report); | ||
| // eslint-disable-next-line @typescript-eslint/no-deprecated |
There was a problem hiding this comment.
❌ CONSISTENCY-5 (docs)
This newly added eslint-disable-next-line lacks a justification comment explaining why the rule is disabled. Other files in this PR include tracking comments (e.g., // This will be fixed as follow up https://github.com/Expensify/App/pull/75357).
Add a comment above or on the same line explaining the reason for the disable, for example:
// This will be fixed as follow up https://github.com/Expensify/App/pull/75357
// eslint-disable-next-line @typescript-eslint/no-deprecated
const currentChatName = getReportName({report});Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.
There was a problem hiding this comment.
Ignore lint check because we just need to refactor the getReportName function
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppAndroid: mWeb ChromeiOS: HybridAppiOS: mWeb SafariMacOS: Chrome / Safari |
|
We did not find an internal engineer to review this PR, trying to assign a random engineer to #66411 as well as to this PR... Please reach out for help on Slack if no one gets assigned! |
|
cc @tgolen |
| reports?: Report[]; | ||
| policies?: Policy[]; | ||
| isReportArchived?: boolean; | ||
| conciergeReportID?: string; |
There was a problem hiding this comment.
It would be really great if there were more explicit comments on the parameters in the type so people understand what their purpose is and when it's OK to pass it or not. Could you please add that for the two new parameters? Bonus points if you do it for all the parameters!
There was a problem hiding this comment.
In this PR, I just updated the GetReportNameParams type so I've added the comments for reportAttributes and conciergeReportID. Can you please check again?
tgolen
left a comment
There was a problem hiding this comment.
That's nice. Thanks! This PR picked up a conflict in the meantime
|
@tgolen Done |
|
🚧 @tgolen has triggered a test Expensify/App build. You can view the workflow run here. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
|
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🚀 Deployed to staging by https://github.com/tgolen in version: 9.3.28-0 🚀
|
|
🚀 Deployed to staging by https://github.com/tgolen in version: 9.3.30-0 🚀
|
|
🚀 Deployed to production by https://github.com/blimpich in version: 9.3.30-3 🚀
|
Explanation of Change
Fixed Issues
$ #66411
PROPOSAL:
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectioncanBeMissingparam foruseOnyxtoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-02-23.at.15.29.58.mov