fix: grid not showing in swap confirmation modal

[0xneves]

Bug Fixes

TL;DR

• Fixed missing grid on swap confirmation modal
• Fixed grid glitches regarding overflow(scrolling)
• Commented on empty cards logic for the grids

Changes:

• added the grid sizes to the card
• added a new type called isConfirmationModal for confirmations when creating swaps in the swap station and when confirming accept swaps in swap offers. This boolean will define a single line of 5 squares
• changed the laptop/desktop squares from 4 to 3. They were being overflowed/cutted from the frame
• commented the entire placeholder code/logic
• removed unnecessary Math when calculating emptySquaresCount
• fixed overflows on offerSummary, hidden for X and auto for Y
• fixed gap for mobile-s (was cutting out of the frame)
• removed the scroll from the grids in all the offerSummary

[vercel]

@0xneves is attempting to deploy a commit to the Shared Blockful's projects Team on Vercel.

A member of the Team first needs to authorize it.

[heronlancellot]

hey yo @0xneves ! I can't test for some reason IDk with the GH the PR.. probably because you made by your develop branch

I would like to add in TokenLists that:

• Old

    <div key={`token-${index}`}>
      <TokenCard
        styleType={tokenCardStyleType}
        onClickAction={tokenCardClickAction}
        displayERC20TokensAmount={displayERC20TokensAmount}
        openTokenAmountSelectionModal={openTokenAmountSelectionModal}
        withSelectionValidation={withSelectionValidation}
        ownerAddress={ownerAddress}
        tokenData={token}
      />
    </div>

• New
  • Remove the key div and put the key in tokenCard. Just one another update to this pr

<TokenCard
        key={index}
        styleType={tokenCardStyleType}
        onClickAction={tokenCardClickAction}
        displayERC20TokensAmount={displayERC20TokensAmount}
        openTokenAmountSelectionModal={openTokenAmountSelectionModal}
        withSelectionValidation={withSelectionValidation}
        ownerAddress={ownerAddress}
        tokenData={token}
 />

[eduramme]

Cool!

[eduramme]

@0xneves By the way, I wasn't able to test as well. But it looks OK from the code perspective

[FrancoAguzzi]

This logic is looking pretty complex. I will approve this PR now since I understand that refactoring it would be more painful than what we can handle atm. Let's come back to this logic later and rethink some things.