Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: APP-556 orders UI #2597

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

fix: APP-556 orders UI #2597

wants to merge 2 commits into from

Conversation

blushi
Copy link
Member

@blushi blushi commented Feb 11, 2025

Description

Closes: https://regennetwork.atlassian.net/browse/APP-556


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • provided a link to the relevant issue or specification
  • provided instructions on how to test
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

How to test

https://deploy-preview-2597--regen-marketplace.netlify.app/dashboard/admin/my-orders
Log in with an account that has made some crypto and/or fiat orders and check out your orders.

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items
.

I have...

  • confirmed all author checklist items have been addressed
  • reviewed code correctness and readability
  • verified React components follow DRY principles
  • reviewed documentation is accurate
  • reviewed tests
  • manually tested (if applicable)

Copy link

netlify bot commented Feb 11, 2025

Deploy Preview for regen-website ready!

Name Link
🔨 Latest commit 0836f5f
🔍 Latest deploy log https://app.netlify.com/sites/regen-website/deploys/67ab61e94f619f00080c3aa2
😎 Deploy Preview https://deploy-preview-2597--regen-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Feb 11, 2025

Deploy Preview for terrasos ready!

Name Link
🔨 Latest commit 0836f5f
🔍 Latest deploy log https://app.netlify.com/sites/terrasos/deploys/67ab61e93419f30008d54f24
😎 Deploy Preview https://deploy-preview-2597--terrasos.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@blushi blushi requested a review from r41ph February 11, 2025 14:43
@blushi
Copy link
Member Author

blushi commented Feb 11, 2025

@erikalogie @S4mmyb see testing instructions

@erikalogie
Copy link
Collaborator

Looks good, just the tooltip icon is not in the right place, if it is possible to put it here:
Monosnap Regen Marketplace 2025-02-11 11-09-46

Also the "?" icon doesn't need to be bigger, it looks bigger now.

@blushi
Copy link
Member Author

blushi commented Feb 11, 2025

Looks good, just the tooltip icon is not in the right place, if it is possible to put it here: Monosnap Regen Marketplace 2025-02-11 11-09-46

Also the "?" icon doesn't need to be bigger, it looks bigger now.

@erikalogie I've just made it look like it is in the comps:
image

@erikalogie
Copy link
Collaborator

Looks good, just the tooltip icon is not in the right place, if it is possible to put it here: Monosnap Regen Marketplace 2025-02-11 11-09-46
Also the "?" icon doesn't need to be bigger, it looks bigger now.

@erikalogie I've just made it look like it is in the comps: image

Oh you are right, whoops. All good then.

Copy link
Contributor

@r41ph r41ph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated to this change, but I noticed that in Order.SummaryRow.tsx:28 the <p> shouldn't be a <p> because in some situations we end up with a <p> as a descendant of this <p>. Would it make sense to update it in this PR, or should we create a separate issue for it?

@@ -138,7 +138,7 @@ export const Order = ({ orderData, allowedDenoms, className }: OrderProps) => {
title={
<Title
variant="h2"
className="mt-10 sm:mt-0 mb-5 text-[21px] leading-[1.5]"
className="mt-10 md:mt-0 mb-5 text-[21px] leading-[1.5]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title still gets too close to the buttons, maybe a bit of padding will sort it out:

...
 <Title
    variant="h2"
    className="... pr-10"
...

I believe it's the same with the <ProjectPlaceInfo> below in line 150, still classes with the buttons:

...
subheader={
   <>
      <div className="... pr-10">
...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re the above comment:
Screenshot 2025-02-13 at 11 43 57
Screenshot 2025-02-13 at 11 44 18

Also, I've noticed that prices can get too long and get cut in some screen sizes. Should this be 6 decimals max @blushi?
Screenshot 2025-02-13 at 11 39 08

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this might be a float precision issue again, thanks for catching

@blushi
Copy link
Member Author

blushi commented Feb 13, 2025

Unrelated to this change, but I noticed that in Order.SummaryRow.tsx:28 the <p> shouldn't be a <p> because in some situations we end up with a <p> as a descendant of this <p>. Would it make sense to update it in this PR, or should we create a separate issue for it?

You mean a div descendant of p?

image

@r41ph
Copy link
Contributor

r41ph commented Feb 13, 2025

You mean a div descendant of p?

Check in Payment Info. There is a <p> descendant of a <p>

Screenshot 2025-02-13 at 16 40 49

@blushi
Copy link
Member Author

blushi commented Feb 13, 2025

You mean a div descendant of p?

Check in Payment Info. There is a <p> descendant of a <p>

Screenshot 2025-02-13 at 16 40 49

Ok I see, so we should probably replace the outer p and it will solve both of these issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants