-
Notifications
You must be signed in to change notification settings - Fork 367
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-7294] - Add AGLB Routes Step to Full Create Flow #9997
upcoming: [M3-7294] - Add AGLB Routes Step to Full Create Flow #9997
Conversation
Coverage Report: ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks awesome! great work Banks 🎉
✅ verified adding, removing, editing routes
✅ verified unit tests
A couple things I noticed, but they might be unrelated to this PR/out of scope:
The search bar
a) changes size whenever I start typing in it
b) a console error pops up -- changing from uncontrolled to controlled input (you can see in the video it pops up)
This is an issue on the Service Targets part too
search bar size change | console error |
---|---|
Screen.Recording.2023-12-18.at.4.41.42.PM.mov |
|
||
const allOtherRoutes = values.configurations.reduce<RoutePayload[]>( | ||
(acc, configuration, configIndex) => { | ||
const otherRoutes = configuration.routes!.filter((r, index) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const otherRoutes = configuration.routes!.filter((r, index) => { | |
const otherRoutes = configuration.routes!.filter((_, index) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a very small nitpick so feel free to ignore lol
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/ServiceTargetDrawer.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested:
- This was looking good from my testing of adding HTTP/S and TCP routes, updating, and removing routes in the AGLB full create flow, and checking for label uniqueness and validation.
- Tests are passing.
- Confirmed no console errors - thanks for fixing the uncontrolled input error Connie mentioned; I'd noticed that too. 🙏🏼
Question:
- What prompted the UX request to scope service targets to each configuration?
Non-blocking:
- Let's do a find and replace on "handleAddServiceTraget" and "handleEditServiceTraget" to correct typos. I suggested changes as I saw them reading through the code, but likely missed some.
- Agreed that that search bar size change Connie mentioned to accommodate the 'x' looks weird. Can we set it to a constant width at the larger breakpoints?
...ges/manager/src/features/LoadBalancers/LoadBalancerCreate/LoadBalancerConfiguration.test.tsx
Outdated
Show resolved
Hide resolved
...ges/manager/src/features/LoadBalancers/LoadBalancerCreate/LoadBalancerConfiguration.test.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/LoadBalancerConfigurations.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/LoadBalancerConfigurations.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/LoadBalancerConfigurations.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/ServiceTargets.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/ServiceTargets.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/ServiceTargets.test.tsx
Outdated
Show resolved
Hide resolved
size="small" | ||
sx={{ padding: 'unset' }} | ||
> | ||
<CloseIcon sx={{ color: '#aaa !important' }} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know why we have to apply the important custom styling here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was the only way I could easily achieve what the UX mockups showed. As AGLB progresses, I'll likely turn this "filter" TextField into a more reusable component. It's currently duplicated a lot 😖
packages/manager/src/features/LoadBalancers/LoadBalancerCreate/LoadBalancerConfigurations.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the fixes Banks! approving pending Mariah's comments addressed 🎉
Description 📝
Note
This PR adds Routes, but does not support rules yet. I will add rule functionality in a separate PR to keep the size down. Rules are complex because of the drag and drop.
Preview 📷
How to test 🧪
Prerequisites
AGLB Full Create Flow
feature flaghttp://localhost:3000/loadbalancers/create
Verification steps
As an Author I have considered 🤔