Fixing displaying the hold and unhold option in expense report by Tony-MK · Pull Request #60436 · Expensify/App

Tony-MK · 2025-04-17T15:34:16Z

Explanation of Change

Fixed Issues

$ #60111
PROPOSAL: #60111 (comment)

Tests

Go to workspace chat
Submit two or more expenses to the workspace chat.
Go to Reports.
Go to Expense Reports.
Click on the expense reports created in step 2.
Bulk select all the expenses.
Click on the dropdown menu.
Note that the hold option is present, then click it.
Click on the dropdown menu again.
Note that the unhold option is present, then click it.
Click on the dropdown menu again.
Note that the hold option is present.

Verify that no errors appear in the JS console

Offline tests

QA Steps

Go to workspace chat
Submit two or more expenses to the workspace chat.
Go to Reports.
Go to Expense Reports.
Click on the expense reports created in step 2.
From the bottom of the expense report page, click on the + button.
Submit a scanned expense.
Bulk select all the expenses.
Click on the dropdown menu.
Note that the hold option is not present while the last expense is scanning.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

macOS.-.Chrome.mov

MacOS: Desktop

macOS.-.Desktop.mov

melvin-bot · 2025-04-17T15:34:53Z

@allroundexperts 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]

Tony-MK · 2025-04-17T15:43:28Z

@allroundexperts, I could not test it on mobile because it does not allow me to select multiple transactions.

WDYT?

allroundexperts · 2025-04-21T23:55:47Z

@Tony-MK Can you please fix the lint issues first?

Tony-MK · 2025-04-22T16:40:46Z

@allroundexperts, I fixed the lint.

You can review it now.

allroundexperts · 2025-04-23T22:11:38Z

Conflicts again 😢

Tony-MK · 2025-04-24T21:50:18Z

Sorry about @allroundexperts.

It is ready.

allroundexperts · 2025-04-27T20:39:20Z

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 that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- 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 there are no new alerts related to the canBeMissing param for useOnyx
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

Screen.Recording.2025-05-01.at.1.51.24.AM.mov

Android: mWeb Chrome

Screen.Recording.2025-05-01.at.1.50.13.AM.mov

iOS: Native

Screen.Recording.2025-05-01.at.1.47.09.AM.mov

iOS: mWeb Safari

Screen.Recording.2025-05-01.at.1.45.26.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-04-28.at.1.49.39.AM.mov

MacOS: Desktop

Screen.Recording.2025-04-28.at.1.54.44.AM.mov

allroundexperts · 2025-04-27T21:00:12Z

BUG

Hold option is initially absent from a scanned receipt expense, but after you visit the expense, and go back to the reports page, the option gets visible.

Screen.Recording.2025-04-28.at.1.58.26.AM.mov

Tony-MK · 2025-04-28T14:01:23Z

@allroundexperts,

I wanted to mention this bug, but thought it was out of scope because based on the video of the OP shows, we are supposed to be fixing displaying the hold/unhold option inside the expense report.

OP Video

1.mp4

Nonetheless, this is a BE bug because the hold/unhold option can't be displayed if the user isOffline and the value of canHold and canUnhold is determined by the BE.

App/src/pages/Search/SearchPage.tsx

Line 239 in 69b2da4

    
           const shouldShowHoldOption = !isOffline && selectedTransactionsKeys.every((id) => selectedTransactions[id].canHold);

App/src/pages/Search/SearchPage.tsx

Line 258 in 69b2da4

    
           const shouldShowUnholdOption = !isOffline && selectedTransactionsKeys.every((id) => selectedTransactions[id].canUnhold);

Furthermore, I was trying to reproduce the issue on the latest main, but I got different results from expected.

First Result

When adding a new scan expense, the merchant text reads scanning.. even if the scan is complete and the hold option is not present.

Skip to 0:56 as I was waiting for the scanning.. to clear, but I realized it was finished when I open the report

1st.mov

Second Result

Right after, I added another scan expense to the previous report, the hold option shows and scanning.. is cleared, even if thought report was not opened.

2nd.mov

allroundexperts · 2025-04-30T21:02:09Z

@Tony-MK Do you know why the following is not working? (It's not working on staging as well)

Screen.Recording.2025-05-01.at.2.00.57.AM.mov

Tony-MK · 2025-04-30T22:30:55Z

Yeah, I noticed it.

It's expected.

allroundexperts

Looks good to me. Let's fix #60436 (comment) as follow up. @marcaaron let us know if you agree.

OSBotify · 2025-05-01T02:52:31Z

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

dangrous · 2025-05-01T18:23:04Z

Hi! Coming here from a backend server error which looks like it's getting hit when you tested this on mobile - the timing and email address for one attempt line up perfectly with this video. If it helps, the error is that HoldMoneyRequestOnSearch is being called with an empty transactionIDList, it looks like the search context might be getting wiped when the new RHP is opened (in the vid it flashes to 0 selected). When you've got a PR up to fix that, would love to follow along!

@marcaaron the error is this one - https://github.com/Expensify/Expensify/issues/495613

marcaaron · 2025-05-01T18:48:07Z

@dangrous We will see if this becomes a ND deploy blocker from QA soon, but sounds like it should be. Thoughts @Tony-MK ?

@allroundexperts, I could not test it on mobile because it does not allow me to select multiple transactions.

What does it mean exactly? I'm guessing that whatever you are experienced there is what triggered the BE error. Seems like it also happens on production or staging server, but what about production App?

marcaaron · 2025-05-01T18:57:29Z

Also, I think if you have ENVIRONMENT=development in the .env these errors are not produced in the future. Though, I see that QA also produced it on staging in this case.

allroundexperts · 2025-05-01T19:14:26Z

@dangrous @marcaaron As mentioned here, this is an error happening on main as well. Should we fix it as a follow up?

#60436 (comment)

marcaaron · 2025-05-01T19:41:14Z

I think I'd be more concerned about the production and staging behaviors than what is happening on main.

github-actions · 2025-05-01T20:06:46Z

🚀 Deployed to staging by https://github.com/marcaaron in version: 9.1.39-0 🚀

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

dangrous · 2025-05-02T20:35:33Z

I think I'd be more concerned about the production and staging behaviors than what is happening on main.

Based on the logs it seems like it's happening in staging too? At least I'm getting the same errors from applause testers.

aldo-expensify · 2025-05-04T11:17:50Z

src/hooks/useSelectedTransactionsActions.ts

+            canHoldTransactions = canHoldTransactions && canHoldRequest;
+            canUnholdTransactions = canUnholdTransactions && canUnholdRequest;
+
+            return !(canHoldTransactions || canUnholdTransactions);


@Tony-MK What is this return value supposed to do? This callback is used in a forEach so the return is ignored... is this logic correct? Maybe what you wanted was to use some?

It should be correct because the return value is only used to stop iterating forEach when canHoldTransactions || canUnholdTransactions is false, meaning we can not hold or unhold all selected transactions.

So, forEach can stop early instead of iterating over all transactions twice, like when using some.

If there is a problem with this method, we can revert to using some.

I don't think that is how forEach works. forEach ignores the value returned by the callback:

There is no way to stop or break a forEach() loop other than by throwing an exception. If you need such behavior, the forEach() method is the wrong tool.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach

Your correct. So, sorry about that.

Should I open a PR to revert forEach to some?

no problem!

I'm not so sure really, using some just because it will stop when you return true from the callback and ignoring the return of selectedTransactions.some(...) doesn't sound so clean to me either. Maybe you should just keep the forEach but drop the returned values so the code doesn't look weird.

selectedTransactions.forEach((selectedTransaction) => { if (!canHoldTransactions && !canHoldTransactions) { return; } if (!selectedTransaction?.transactionID) { canHoldTransactions = false; canUnholdTransactions = false; return; } const iouReportAction = getIOUActionForTransactionID(reportActions, selectedTransaction.transactionID); const {canHoldRequest, canUnholdRequest} = canHoldUnholdReportAction(iouReportAction); canHoldTransactions = canHoldTransactions && canHoldRequest; canUnholdTransactions = canUnholdTransactions && canUnholdRequest; });

I wouldn't care much for iterating the rest of the elements.. you can add something like

if (!canHoldTransactions && !canHoldTransactions) { return; }

to make it fast, and it is also already inside a useMemo so this shouldn't happen all the time.

Tony-MK · 2025-05-04T13:59:14Z

Hi! Coming here from a backend server error which looks like it's getting hit when you tested this on mobile - the timing and email address for one attempt line up perfectly with #60436 (comment). If it helps, the error is that HoldMoneyRequestOnSearch is being called with an empty transactionIDList, it looks like the search context might be getting wiped when the new RHP is opened (in the vid it flashes to 0 selected)

Hey @dangrous and @marcaaron, I did some digging to answer your questions.

It is not related to this PR but this PR because it introduced clearSelectedTransactions in handleOnModalHide without a condition to return early.

Then, this CP Stag PR introduced shouldPreserveSelectionAfterHideModal.

Except for the delete option, shouldPreserveSelectionAfterHideModal was left out for some of the headerButtonsOptions in SearchPage

App/src/pages/Search/SearchPage.tsx

Lines 241 to 247 in 74b93b9

    
           if (shouldShowHoldOption) { 
        
               options.push({ 
        
                   icon: Expensicons.Stopwatch, 
        
                   text: translate('search.bulkActions.hold'), 
        
                   value: CONST.SEARCH.BULK_ACTION_TYPES.HOLD, 
        
                   shouldCloseModalOnSelect: true, 
        
                   onSelected: () => {

App/src/pages/Search/SearchPage.tsx

Lines 279 to 286 in 74b93b9

    
           if (shouldShowDeleteOption) { 
        
               options.push({ 
        
                   icon: Expensicons.Trashcan, 
        
                   text: translate('search.bulkActions.delete'), 
        
                   value: CONST.SEARCH.BULK_ACTION_TYPES.DELETE, 
        
                   shouldCloseModalOnSelect: true, 
        
                   shouldPreserveSelectionAfterHideModal: true, 
        
                   onSelected: () => {

Therefore, in SearchSelectedNarrow, when the hold or unhold option is clicked, clearSelectedTransactions is called, clearing the selectedTransactions.

App/src/pages/Search/SearchSelectedNarrow.tsx

Lines 34 to 38 in 74b93b9

    
           options[selectedOptionIndexRef.current]?.onSelected?.(); 
        
           if (options[selectedOptionIndexRef.current]?.shouldPreserveSelectionAfterHideModal) { 
        
               return; 
        
           } 
        
           clearSelectedTransactions();

Thus, sending an empty list for transactionIDList in HoldMoneyRequestOnSearch's payload

When you've got a PR up to fix that, would love to follow along

Since it's also happening on staging and production, should I raise a PR?

However, I'm unsure due to this comment.

dangrous · 2025-05-05T15:42:31Z

It looks like they've got a PR up that will fix that behavior, I'll ping there and make sure they test against this flow.

Thank you for the investigation! Nice work, I think you're off the hook :)

github-actions · 2025-05-06T01:04:39Z

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.1.39-8 🚀

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

luacmartins · 2025-05-15T15:44:45Z

BTW we were working on a BulkHoldRequest API and that's why we had this limitation in place, to avoid doing N API requests when holding multiple transactions like we did in this PR

Tony-MK · 2025-05-15T17:49:29Z

BTW we were working on a #59683 and that's why we had this limitation in place, to avoid doing N API requests when holding multiple transactions like we did in this PR

Sorry, I wasn't aware of that at first. I attempted to revert my mistake here.

App/src/pages/Search/SearchMoneyRequestReportHoldReasonPage.tsx

Line 23 in 259c21f

    
           selectedTransactionsID.forEach((transactionID) => putOnHold(transactionID, values.comment, reportID));

Should I revert the line? But it seems better to use the new API.

Thoughts?

luacmartins · 2025-05-15T18:05:05Z

@Tony-MK yea, let's just use the new API. We don't have a PR up for that yet

Tony-MK · 2025-05-15T18:23:57Z

You mentioned here that the new API is in place.

Can I raise a PR for the fix?

luacmartins · 2025-05-16T20:31:46Z

Yes, please

Tony-MK · 2025-05-18T21:58:30Z

@luacmartins

Great. I started working on the PR, but could you give me some details about the BulkHoldRequest, such as the endpoint and parameters required?

Thanks

luacmartins · 2025-05-19T14:45:43Z

@Tony-MK sure:

API endpoint: BulkHoldRequest
BulkHoldRequestParams: {
    holdData: string; // This is a json object with shape Record<string, HoldDataEntry>;
    comment: string;
}

type HoldDataEntry = {
  transactionThreadReportID?: string;
  transactionThreadCreatedReportActionID?: string;
  holdReportActionID: string;
  commentReportActionID: string;
};

The key for holdData is the transactionID and transactionThreadReportID and transactionThreadCreatedReportActionID are only passed as params if they were optimistically created as part of the hold

Tony-MK added 2 commits April 17, 2025 18:13

fixing hold and unhold options in MoneyReportHeader.tsx

9ff743f

Holding all request reports..

9817bb9

Tony-MK marked this pull request as ready for review April 17, 2025 15:34

Tony-MK requested a review from a team as a code owner April 17, 2025 15:34

melvin-bot bot requested review from allroundexperts and removed request for a team April 17, 2025 15:34

Tony-MK added 3 commits April 17, 2025 18:39

typos...

8c2c1a5

typos ...

3bae508

updating imports in MoneyReportHeader.tsx

2ac740b

Tony-MK mentioned this pull request Apr 17, 2025

[Due for payment 2025-05-13] [$250] Expense Reports - Hold option is not present when the expenses are bulk selected #60111

Closed

8 tasks

Tony-MK added 4 commits April 22, 2025 18:10

Merge branch 'main' of https://github.com/Expensify/App into fix/60111

ac649ca

lint..

749e16c

typechecks..

4a7de48

prettier...

5c55981

Merge branch 'main' into fix/60111

c30c710

Tony-MK added 2 commits April 24, 2025 23:29

Merge branch 'main' of https://github.com/Expensify/App into fix/60111

e8b5f7a

prettier...

a3d384b

Tony-MK mentioned this pull request Apr 26, 2025

[$250] Expense - Unhold option is available for user who does not hold the expense which causes error #60845

Closed

18 tasks

Tony-MK changed the title ~~Fix/60111~~ Fixing displaying the hold and unhold option in expense report. Apr 28, 2025

Tony-MK changed the title ~~Fixing displaying the hold and unhold option in expense report.~~ Fixing displaying the hold and unhold option in expense report Apr 28, 2025

Merge branch 'main' into fix/60111

675bfba

allroundexperts approved these changes May 1, 2025

View reviewed changes

melvin-bot bot requested a review from marcaaron May 1, 2025 00:58

marcaaron approved these changes May 1, 2025

View reviewed changes

marcaaron assigned Tony-MK May 1, 2025

marcaaron merged commit d196f8e into Expensify:main May 1, 2025
19 of 20 checks passed

github-actions bot mentioned this pull request May 1, 2025

Deploy Checklist: New Expensify 2025-05-01 #61263

Closed

61 tasks

aldo-expensify reviewed May 4, 2025

View reviewed changes

dangrous mentioned this pull request May 5, 2025

Fix clearing selection when mobile selection mode is on #61377

Merged

51 tasks

Tony-MK mentioned this pull request May 6, 2025

Refractoring selected transactions loop #61482

Merged

51 tasks

Tony-MK mentioned this pull request May 19, 2025

Bulk hold #62329

Merged

51 tasks

Conversation

Tony-MK commented Apr 17, 2025 • edited by marcaaron Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Apr 17, 2025

Uh oh!

Tony-MK commented Apr 17, 2025

Uh oh!

allroundexperts commented Apr 21, 2025

Uh oh!

Tony-MK commented Apr 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

allroundexperts commented Apr 23, 2025

Uh oh!

Tony-MK commented Apr 24, 2025

Uh oh!

allroundexperts commented Apr 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

allroundexperts commented Apr 27, 2025

Uh oh!

Tony-MK commented Apr 28, 2025

Uh oh!

allroundexperts commented Apr 30, 2025

Uh oh!

Tony-MK commented Apr 30, 2025

Uh oh!

allroundexperts left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented May 1, 2025

Uh oh!

dangrous commented May 1, 2025

Uh oh!

marcaaron commented May 1, 2025

Uh oh!

marcaaron commented May 1, 2025

Uh oh!

allroundexperts commented May 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

marcaaron commented May 1, 2025

Uh oh!

github-actions bot commented May 1, 2025

Uh oh!

dangrous commented May 2, 2025

Uh oh!

aldo-expensify May 4, 2025

Choose a reason for hiding this comment

Uh oh!

Tony-MK May 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aldo-expensify May 4, 2025

Choose a reason for hiding this comment

Uh oh!

Tony-MK May 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aldo-expensify May 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Tony-MK commented May 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Tony-MK commented Apr 17, 2025 •

edited by marcaaron

Loading

Tony-MK commented Apr 22, 2025 •

edited

Loading

allroundexperts commented Apr 27, 2025 •

edited

Loading

allroundexperts left a comment •

edited

Loading

allroundexperts commented May 1, 2025 •

edited

Loading

Tony-MK May 4, 2025 •

edited

Loading

Tony-MK May 4, 2025 •

edited

Loading

aldo-expensify May 5, 2025 •

edited

Loading

Tony-MK commented May 4, 2025 •

edited

Loading

luacmartins commented May 15, 2025 •

edited

Loading

Tony-MK commented May 15, 2025 •

edited

Loading

Tony-MK commented May 18, 2025 •

edited

Loading

luacmartins commented May 19, 2025 •

edited

Loading