fix: musd deposit page for new MM Pay designs cp-7.74.0#28654
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
| (amountHuman: string) => <MusdOverrideContent amountHuman={amountHuman} />, | ||
| [], | ||
| ); | ||
| const renderOverrideContent = useCallback(() => null, []); |
There was a problem hiding this comment.
Can we remove this if we don't render anything?
There was a problem hiding this comment.
This is used in <CustomAmountInfo in couple of places and can not be removed.
There was a problem hiding this comment.
Isn't this an optional value? Not asking to remove functionality but removing prop below.
There was a problem hiding this comment.
It is used at couple of decision points in CustomAmountInfo and we have removed only 1. The value is used in CustomAmountInfo and not possible to remove.
There was a problem hiding this comment.
@jpuri I am not asking to remove it from CustomAmountInfo, my question is remove using empty callback. MusdConversionInfo component can return as below and it won't cause any issue, meaning
const renderOverrideContent = useCallback(() => null, []); can be removed.
return (
<CustomAmountInfo
preferredToken={preferredPaymentToken}
hasMax
onAmountSubmit={startQuoteTrace}
/>
);
There was a problem hiding this comment.
Yes it can not be removed, as it is used at couple of places in CustomAmountInfo, not for rendering but more as boolean check to see if it is defined.
There was a problem hiding this comment.
I replaced by a boolean prop hidePayTokenAmount
| @@ -1,46 +1,16 @@ | |||
| import React, { useCallback, useEffect } from 'react'; | |||
| import { useParams } from '../../../../../../util/navigation/navUtils'; | |||
| import OutputAmountTag from '../../../../../UI/Earn/components/OutputAmountTag'; | |||
There was a problem hiding this comment.
Can we also remove this component entirely?
There was a problem hiding this comment.
We do not own it, I would avoid removing it.
There was a problem hiding this comment.
No point of leaving dead code either. Can you create a follow up task for them then?
There was a problem hiding this comment.
Can you push the task here for reference?
Related thread of confirmation from PMs: https://consensys.slack.com/archives/C0A917EJME0/p1775819724642599?thread_ts=1775767602.266489&cid=C0A917EJME0
| (amountHuman: string) => <MusdOverrideContent amountHuman={amountHuman} />, | ||
| [], | ||
| ); | ||
| const renderOverrideContent = useCallback(() => null, []); |
There was a problem hiding this comment.
Isn't this an optional value? Not asking to remove functionality but removing prop below.
| @@ -1,46 +1,16 @@ | |||
| import React, { useCallback, useEffect } from 'react'; | |||
| import { useParams } from '../../../../../../util/navigation/navUtils'; | |||
| import OutputAmountTag from '../../../../../UI/Earn/components/OutputAmountTag'; | |||
There was a problem hiding this comment.
No point of leaving dead code either. Can you create a follow up task for them then?
…sk-mobile into much_deposit_fix
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7fe90fb. Configure here.
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection: Key impacts:
The changes are unit-tested and the refactoring is straightforward, but the shared nature of Performance Test Selection: |
|
|
✅ E2E Fixture Validation — Schema is up to date |




Description
Fix design of mush deposit page.
Changelog
CHANGELOG entry:
Related issues
Fixes: https://consensyssoftware.atlassian.net/browse/CONF-1173
Manual testing steps
Screenshots/Recordings
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Low risk UI/prop change limited to the confirmations custom amount view and mUSD conversion flow; main risk is unintended layout/row visibility regressions when
hidePayTokenAmountis enabled.Overview
Updates
CustomAmountInfoto removeoverrideContentand introducehidePayTokenAmount, which hides the defaultPayTokenAmount(and the associated extra content block) while keepingPayWithRowrendering logic consistent.Simplifies
MusdConversionInfoby deleting the bespoke override UI (output tag + embeddedPayWithRow) and instead passinghidePayTokenAmounttoCustomAmountInfo; tests are updated accordingly.Reviewed by Cursor Bugbot for commit 3c829f9. Bugbot is set up for automated code reviews on this repo. Configure here.