-
Notifications
You must be signed in to change notification settings - Fork 369
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-9095] - Add Linode Interfaces Table to Linode Details #11655
base: develop
Are you sure you want to change the base?
upcoming: [M3-9095] - Add Linode Interfaces Table to Linode Details #11655
Conversation
Coverage Report: ✅ |
Cloud Manager UI test results🎉 508 passing tests on test run #8 ↗︎
|
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 Banks! doing a quick initial review while I wait for docker - brb
<Table> | ||
<TableHead> | ||
<TableRow> | ||
<TableCell>ID</TableCell> | ||
<TableCell>Type</TableCell> | ||
<TableCell>MAC Address</TableCell> | ||
<TableCell>Version</TableCell> | ||
<TableCell>Updated</TableCell> | ||
<TableCell>Created</TableCell> | ||
<TableCell /> | ||
</TableRow> | ||
</TableHead> |
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.
nit: in terms of naming, it seems like this should go in LinodeInterfacesTable
too since it's part of the table
return 'public'; | ||
}; | ||
|
||
export type InterfaceType = ReturnType<typeof getLinodeInterfaceType>; |
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.
could we update this name to LinodeInterfaceType? that way if someone else sees it they don't think 'configuration profile interface vs linodeInterface'
export type InterfaceType = ReturnType<typeof getLinodeInterfaceType>; | |
export type LinodeInterfaceType = ReturnType<typeof getLinodeInterfaceType>; |
const { linodeId } = useParams<{ linodeId: string }>(); | ||
const _linodeId = Number(linodeId); | ||
|
||
return ( | ||
<Stack spacing={2}> | ||
<LinodeNetworkingSummaryPanel linodeId={_linodeId} /> | ||
<LinodeFirewalls linodeID={_linodeId} /> | ||
{!isLinodeInterfaceEnabled && <LinodeFirewalls linodeID={_linodeId} />} |
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.
are we planning to hide LinodeFirewalls for LinodeInterfaces / should we check with UX? I can assign [M3-9317] to you if you're planning to tackle it 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.
@@ -18,6 +18,7 @@ export default defineConfig({ | |||
}, | |||
}, | |||
server: { | |||
allowedHosts: ['cloud.lindev.local'], |
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.
🚀
oh I forgot to comment - I was able to see the network interfaces table! ✅ will return for a final review after firewall column is added |
Description 📝
Preview 📷
How to test 🧪
Prerequisites
Verification steps
Note
The UX mockup only included a type and MAC Addresss column.... I added more columns because I figured it can't hurt. We can refine as the project evolves but I don't see any reason to hide things from the user.
I'm surprised we're not showing the Interfaces IP addresses or attached firewall in the table row. I have a feeling we will want this... I'll ask UX next time we sync, but this isn't a blocker. We'll come back and refine as needed
Author Checklists
As an Author, to speed up the review process, I 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
As an Author, before moving this PR from Draft to Open, I confirmed ✅