[UI - Wallet Stability] Create new SQ/StatusAmountInputPanel for SendModal / BridgeModal / SwapModal

[noeliaSD]

Design

• Replacement for AmountToSend and AmountToReceive (maybe we can do the replacement here or keep the integration for task [UI - Wallet Stability] Refactor SendModal to use the new / reworked components #15215)
• Generic SQ component (some basic api, but needs design check / analysis):
  • Property to allow being aligned to the left or to the right
  • Title
  • Editable input but can be also readonly
  • Subtitle
  • Status: ok / failure
• Storybook page without warnings
• No stores dependencies
• Create qml tests for the component

[caybro]

Oh that's a new one! I like it, would definitely be a better replacement for the SwapModal/SwapInputPanel component

[caybro]

Just a reminder, this is also used in SwapModal like this: AmountToSend -> SwapInputPanel -> SwapModal

[noeliaSD]

As decided in our sync, maybe better to create a separate and new component, only apply this new component to send and bridge AND create a separate task to do the integration of the new component to swap for the next milestone.

[Khushboo-dev-cpp]

@micieslak as discussed, this is also something swap needs as we currently use double within the current AmountToSendInput and it causes loss of precision, As I understand from @noeliaSD the work done here will not be used in swap but a different issue will be created for it. Would be great if we can create a task for it so that its not forgotten :)

[caybro]

@micieslak as discussed, this is also something swap needs as we currently use double within the current AmountToSendInput and it causes loss of precision, As I understand from @noeliaSD the work done here will not be used in swap but a different issue will be created for it. Would be great if we can create a task for it so that its not forgotten :)

We don't really use a double here (but the rawValue based on the Big number) in SwapModal

[Khushboo-dev-cpp]

@micieslak as discussed, this is also something swap needs as we currently use double within the current AmountToSendInput and it causes loss of precision, As I understand from @noeliaSD the work done here will not be used in swap but a different issue will be created for it. Would be great if we can create a task for it so that its not forgotten :)

We don't really use a double here (but the rawValue based on the Big number) in SwapModal

status-desktop/ui/imports/shared/popups/send/views/AmountToSend.qml

Line 62 in c8744cf

property double cryptoValueToSend

[caybro]

@micieslak as discussed, this is also something swap needs as we currently use double within the current AmountToSendInput and it causes loss of precision, As I understand from @noeliaSD the work done here will not be used in swap but a different issue will be created for it. Would be great if we can create a task for it so that its not forgotten :)

We don't really use a double here (but the rawValue based on the Big number) in SwapModal

status-desktop/ui/imports/shared/popups/send/views/AmountToSend.qml

Line 62 in c8744cf

property double cryptoValueToSend

Yes, but in SwapModal we use the "text" for display, and rawValue when sending the transaction right?

But general yeah, there should be ideally no floats/doubles around in that code

[Khushboo-dev-cpp]

@micieslak as discussed, this is also something swap needs as we currently use double within the current AmountToSendInput and it causes loss of precision, As I understand from @noeliaSD the work done here will not be used in swap but a different issue will be created for it. Would be great if we can create a task for it so that its not forgotten :)

We don't really use a double here (but the rawValue based on the Big number) in SwapModal

status-desktop/ui/imports/shared/popups/send/views/AmountToSend.qml

Line 62 in c8744cf

property double cryptoValueToSend

Yes, but in SwapModal we use the "text" for display, and rawValue when sending the transaction right?

But general yeah, there should be ideally no floats/doubles around in that code

The thing is that these floats are used to calculate the rawValue in the end and thats whats causing the issue withe losing precision.