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-7609] - Placement Groups Landing Page #10068

Merged
merged 11 commits into from
Jan 19, 2024

Conversation

abailly-akamai
Copy link
Contributor

@abailly-akamai abailly-akamai commented Jan 17, 2024

Description πŸ“

This PR adds core elements for the Placement Group feature, namely basic navigation and a populated landing page

Changes πŸ”„

  • Adds PrimayNav entry w/ Beta Chip
  • Adds a populated landing page with table and rows
  • Tests for components

Preview πŸ“·

Screenshot 2024-01-18 at 14 17 27

How to test πŸ§ͺ

Prerequisites

Verification steps

  • Pull and run code locally
  • in Dev settings, enable both the Placement Groups flag and MSW
  • Click on "Placement Groups" in the menu
  • Confirm the landing page content

As an Author I have considered πŸ€”

Check all that apply

  • πŸ‘€ 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

bottom: -2,
left: 52,
position: 'absolute',
},
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 is to position the beta chip similarly to AGLB menu item since this one also wraps in two lines a bit awkwardly

Copy link
Contributor

Choose a reason for hiding this comment

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

Nice, I had noticed this before our huddle yesterday.

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 is all pretty boilerplate and subject to iterations as we build this feature

@abailly-akamai abailly-akamai marked this pull request as ready for review January 18, 2024 16:50
@abailly-akamai abailly-akamai requested a review from a team as a code owner January 18, 2024 16:50
@abailly-akamai abailly-akamai requested review from jdamore-linode and jaalah-akamai and removed request for a team January 18, 2024 16:50
Copy link

github-actions bot commented Jan 18, 2024

Coverage Report: βœ…
Base Coverage: 79.92%
Current Coverage: 79.93%

@carrillo-erik
Copy link
Contributor

carrillo-erik commented Jan 18, 2024

Tests look good βœ…
Screenshot 2024-01-18 at 11 23 41 AM

Screenshot 2024-01-18 at 11 28 17 AM

Copy link
Contributor

@bnussman-akamai bnussman-akamai left a comment

Choose a reason for hiding this comment

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

General structure looks great! Have just a few small items

Comment on lines +64 to +69
<Link
data-testid={`link-to-placement-group-${id}`}
to={`/placement-groups/${id}`}
>
{label} ({affinityType}) &nbsp;
</Link>
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we push UX to allow us to put affinity_type in its own column? We have plenty of room and this would allow users to order by affinity_type (and maybe filter/seach when we improve our tables)

This also deviates from our normal pattern of keeping the label basic (with no extra information)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good suggestion, but prob not for M1. Couple reasons:

  • The PG label with the affinity appendage will follow you around (it will also be in the PG select, breadcrumb etc). It adds consistency.
  • (for now) the sorting is a bit superfluous considering you only get a max of 5 PGs per account

It might be something we do in the future however as the feature evolves

Copy link
Contributor

Choose a reason for hiding this comment

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

I had the same question, thanks for asking and clarifying. πŸ‘

Copy link
Contributor

@bnussman-akamai bnussman-akamai left a comment

Choose a reason for hiding this comment

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

πŸš€

@abailly-akamai abailly-akamai merged commit 9582ca1 into linode:develop Jan 19, 2024
18 checks passed
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