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

upcoming: [M3-7928] - Linode Create Refactor - Summary - Part 8 #10334

Conversation

bnussman-akamai
Copy link
Contributor

@bnussman-akamai bnussman-akamai commented Mar 29, 2024

Description πŸ“

  • Adds the Summary section to the new Linode Create flow πŸ“„

Preview πŸ“·

Screenshot 2024-03-29 at 4 35 50β€―PM

How to test πŸ§ͺ

Prerequisites

  • Check out this PR
  • Using local dev tools, turn on the Linode Create v2 flag 🎏

Verification steps

  • Test the summary section on the new Linode Create flow
  • Verify it correctly summarizes what options you have selected
  • Verify it behaves the same as the current Linode Create flow (compare to production)
  • Check on smaller screen sizes πŸ“±

As an Author I have considered πŸ€”

  • πŸ‘€ Doing a self review
  • ❔ Our contribution guidelines
  • 🀏 Splitting feature into small PRs
  • βž• Adding a changeset
  • πŸ§ͺ Providing/Improving test coverage
  • πŸ” Removing all sensitive information from the code and PR description
  • 🚩 Using a feature flag to protect the release
  • πŸ‘£ Providing comprehensive reproduction steps
  • πŸ“‘ Providing or updating our documentation
  • πŸ•› Scheduling a pair reviewing session
  • πŸ“± Providing mobile support
  • β™Ώ Providing accessibility support

@bnussman-akamai bnussman-akamai marked this pull request as ready for review April 1, 2024 18:44
@bnussman-akamai bnussman-akamai requested a review from a team as a code owner April 1, 2024 18:44
@bnussman-akamai bnussman-akamai requested review from hana-linode, jaalah-akamai, hkhalil-akamai and abailly-akamai and removed request for a team April 1, 2024 18:44
Comment on lines +123 to +133
<Stack
alignItems="center"
direction="row"
key={item.title}
spacing={1}
>
<Typography fontFamily={(theme) => theme.font.bold}>
{item.title}
</Typography>
{item.details && <Typography>{item.details}</Typography>}
</Stack>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was in the fence about making this stuff into components. I think this file is simple enough to leave it like this, but I'm open to feedback

Copy link
Contributor

Choose a reason for hiding this comment

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

fine by me

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This file handles the entire summary. I'm pretty happy with it but if anyone has better ideas for how to clean it up or improve it let me know

Copy link
Contributor

@hkhalil-akamai hkhalil-akamai left a comment

Choose a reason for hiding this comment

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

Clean! 🧼

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for these thorough tests!

Comment on lines 79 to 85
{
item: {
details: `$${backupsPrice}/month`,
title: 'Backups',
},
show: backupsEnabled,
},
Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure if this is an intentional change or not: in the old flow, backups pricing is show only after the user selects a region. Now, it displays as "$--.--/month"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch. I'll adjust to match the existing behavior.

Copy link

github-actions bot commented Apr 1, 2024

Coverage Report: βœ…
Base Coverage: 81.75%
Current Coverage: 81.75%

Copy link
Contributor

@abailly-akamai abailly-akamai left a comment

Choose a reason for hiding this comment

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

@bnussman-akamai we're missing the placement group summary item

},
show: Boolean(firewallId),
},
];
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: i could see this in a Summary.data.ts file

flexItem
orientation="vertical"
sx={{ borderWidth: 1, margin: 0 }}
/>
Copy link
Contributor

Choose a reason for hiding this comment

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

we're going for parity so it's fine to keep things as is, but i can see a case to use a Grid so we can have several columns on a medium bp? not a big deal either way, we can ask UX.

Screenshot 2024-04-02 at 12 31 09

Screenshot 2024-04-02 at 12 32 19

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't go the grid route, but I improved wrapping so that is is as good as the existing behavior - c2161ab

Screenshot 2024-04-02 at 1 31 58β€―PM

Comment on lines +123 to +133
<Stack
alignItems="center"
direction="row"
key={item.title}
spacing={1}
>
<Typography fontFamily={(theme) => theme.font.bold}>
{item.title}
</Typography>
{item.details && <Typography>{item.details}</Typography>}
</Stack>
Copy link
Contributor

Choose a reason for hiding this comment

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

fine by me

@bnussman-akamai bnussman-akamai merged commit a6d8fa3 into linode:develop Apr 2, 2024
18 checks passed
bnussman-akamai added a commit to bnussman-akamai/manager that referenced this pull request Apr 4, 2024
…de#10334)

* inital summary

* more work and unit tests

* Added changeset: Linode Create Refactor - Summary - Part 8

* only show backups if a type is selected

* add placement group to summary

* fix summary wrapping

---------

Co-authored-by: Banks Nussman <banks@nussman.us>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants