fix(core): improve stellar confirmation screens#6922
Conversation
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. 💤 Files selected but had no reviewable changes (1)
⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThis PR refactors Stellar transaction confirmation flows to improve visual clarity between intermediate and final confirmation screens. The changes introduce a new Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| @@ -0,0 +1 @@ | |||
| Improve Stellar confirmation screens to better distinguish intermediate steps from the final confirmation and polish related layout details. | |||
There was a problem hiding this comment.
Let's shorten it to something like: "Improve Stellar confirmations flows."
| verb=TR.buttons__continue, | ||
| ) | ||
|
|
||
| if amount is not None and asset is not None: |
There was a problem hiding this comment.
If it must be supplied together, please make the function take the type enforcing it, i.e. amount: (str, StellarAsset) | None.
Double-check similar pattern in other function calls please.
There was a problem hiding this comment.
@copilot create a new branch from this one and implement the feedback of this comment. Then create another PR targeting the base branch.




























































































































































fixes #6709
Cherry-picking from #6771
CC @overcat