[HOLD][Part 2] Onyx.connect deprecation in ModifiedExpenseMessage#75562
Open
kubabutkiewicz wants to merge 69 commits intoExpensify:mainfrom
Open
Conversation
melvin-bot
bot
requested review from
heyjennahay and
parasharrajat
and removed request for
a team
|
@parasharrajat 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] |
…to part-3-onyx-connect-deprecate-for-modified-expense-message
Contributor
Author
|
@parasharrajat places wheer I am passing |
Codecov Report✅ Changes either increased or maintained existing code coverage, great job!
|
Member
|
There are some conflicts already @kubabutkiewicz |
54 tasks
Contributor
Author
|
Hi @parasharrajat just fyi I will be ooo till 30 November |
Member
|
Sure. No problem. we will get this today. |
Contributor
|
Not a product change, removing myself and unsubscribing |
…to part-3-onyx-connect-deprecate-for-modified-expense-message
…to part-3-onyx-connect-deprecate-for-modified-expense-message
…to part-3-onyx-connect-deprecate-for-modified-expense-message
Contributor
Author
|
Comments resolved/answered @parasharrajat |
Comment on lines
-696
to
+698
| buildMessageFragmentForValue( | ||
| translate, | ||
| reportActionOriginalMessage?.billable ?? '', | ||
| reportActionOriginalMessage?.oldBillable ?? '', | ||
| translate('iou.expense'), | ||
| true, | ||
| setFragments, | ||
| removalFragments, | ||
| changeFragments, | ||
| ); | ||
| const oldBillable = reportActionOriginalMessage?.oldBillable === 'billable' ? translate('common.billable').toLowerCase() : translate('common.nonBillable').toLowerCase(); | ||
| const newBillable = reportActionOriginalMessage?.billable === 'billable' ? translate('common.billable').toLowerCase() : translate('common.nonBillable').toLowerCase(); | ||
| buildMessageFragmentForValue(translate, newBillable, oldBillable, translate('iou.expense'), true, setFragments, removalFragments, changeFragments); |
Member
There was a problem hiding this comment.
is this change part of this PR?
Contributor
Author
There was a problem hiding this comment.
this is a sync with getForReportAction which you asked yesterday
Comment on lines
+731
to
+737
| // If we don't have enough structured information to build a detailed message but we | ||
| // know the change was AI-generated, fall back to an AI-attributed generic summary so | ||
| // users can still understand that Concierge updated the expense automatically. | ||
| if (reportActionOriginalMessage?.aiGenerated) { | ||
| return `${translate('iou.changedTheExpense')} ${translate('iou.basedOnAI')}`; | ||
| } | ||
|
|
Contributor
Author
There was a problem hiding this comment.
this is a sync with getForReportAction which you asked yesterday
53 tasks
…to part-3-onyx-connect-deprecate-for-modified-expense-message
parasharrajat
approved these changes
Feb 5, 2026
Member
parasharrajat
left a comment
parasharrajat
left a comment
There was a problem hiding this comment.
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 Issuessection 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
Testssection - I verified the steps for Staging and/or Production testing are in the
QA stepssection - 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 verified the steps for local testing are in the
- 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.
toggleReportand notonIconClick). - 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 approved by marketing by adding the
Waiting for Copylabel for a copy review on the original GH to get the correct copy. - 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
- 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.
- 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 usingAvatarhave 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
thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor) - Any internal methods bound to
thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick) - 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
Avataris modified, I verified thatAvataris 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 form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added
Designlabel so the design team can review the changes.
- If a new page is added, I verified it's using the
ScrollViewcomponent to make it scrollable when more elements are added to the page. - If the
mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
05.02.2026_22.49.18_REC.mp4
05.02.2026_22.50.31_REC.mp4
🎀 👀 🎀 C+ reviewed
…to part-3-onyx-connect-deprecate-for-modified-expense-message
Contributor
|
oof, is there no way to break this into smaller PRs? 39 files is real tough. If we need to revert this, it'll be a huge problem. |
…to part-3-onyx-connect-deprecate-for-modified-expense-message
Contributor
Author
|
@danieldoglas unfortunately no, those are changes to add new param to the getValidOptions, which is used in a lot of places in our app and also is used in other function so all changes are connected |
…to part-3-onyx-connect-deprecate-for-modified-expense-message
danieldoglas
changed the title
Contributor
|
Similar to the discussion here we won't be merging this huge PRs for refactors anymore. It's too risky, and if it breaks anything, it will be a problem for deployers to revert this. We need you to break this PR down a bit. One example of how you can break down this PR:
I know this is not what would be easier to implement, but moving forward safely and maintaining our ability to easily revert PRs when we push something that can break code is a priority over doing faster PRs. |
Contributor
|
@parasharrajat I've updated the instructions above. Tagging you specifically because you already reacted to the previous text. Let me know if you have any questions. |
Contributor
Author
|
@danieldoglas could you tell me whats is the priority of this onyx deprecation project? I am asking because I am involved in the critical project of improving the sentry metrics and probably I will need to find someone else to take care of this now. |
Contributor
|
If you can find someone to take this over, it'd be great. |
Contributor
Author
|
Yes we are looking for someone |
53 tasks
53 tasks
This was referenced Mar 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation of Change
Fixed Issues
$#66336
PROPOSAL:
Tests
Click on FAB
Select Start chat
Verify that searching and displaying options is working
Click on FAB
Select Create Expense
Use manual or scan
Go to workspace selection
Search something
Verify that options are showed correctly
Offline tests
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
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
MacOS: Desktop