-
Notifications
You must be signed in to change notification settings - Fork 391
upcoming: [DI-28750] - Add edit feature for notification channels #13235
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: [DI-28750] - Add edit feature for notification channels #13235
Conversation
bnussman-akamai
left a comment
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.
Just left a few minor suggestions
| return ( | ||
| <> | ||
| <Breadcrumb crumbOverrides={overrides} pathname={pathname} /> | ||
| <Box alignContent="center" height="600px"> |
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 might be okay but maybe a minHeight would serve us better and save us from potentional overflow issues in the longer run
| * @param crumbOverrides - The overrides to be provided in breadcrumb | ||
| * @param children - The message component (e.g., CircleProgress, ErrorState, or Placeholder) | ||
| */ | ||
| const EditChannelState = ({ |
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.
A better name may be something like EditChannelContainer
|
|
||
| const cloudPulseNotificationChannelEditRoute = createRoute({ | ||
| getParentRoute: () => cloudPulseAlertsRoute, | ||
| path: 'notification-channels/edit/$channelId', |
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.
Params should be parsed here. That will make it so that we don't need to cast the string to a number everywhere in the app
| path: 'notification-channels/edit/$channelId', | |
| path: 'notification-channels/edit/$channelId', | |
| params: { | |
| parse: (rawParams) => ({ | |
| channelId: Number(rawParams.channelId), | |
| }), | |
| }, |
| export const useNotificationChannelQuery = (channelId: number) => { | ||
| return useQuery<NotificationChannel, APIError[]>({ | ||
| ...queryFactory.notificationChannels._ctx.channelById(channelId), | ||
| }); | ||
| }; |
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: We could remove the spread operation here
| export const useNotificationChannelQuery = (channelId: number) => { | |
| return useQuery<NotificationChannel, APIError[]>({ | |
| ...queryFactory.notificationChannels._ctx.channelById(channelId), | |
| }); | |
| }; | |
| export const useNotificationChannelQuery = (channelId: number) => { | |
| return useQuery<NotificationChannel, APIError[]>( | |
| queryFactory.notificationChannels._ctx.channelById(channelId) | |
| ); | |
| }; |
| if (!channelData) { | ||
| return <StyledPlaceholder icon={EntityIcon} title="No Data to display." />; | ||
| } | ||
| return <NullComponent />; |
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: we could just use null
| return <NullComponent />; | |
| return null; |
…anager into feature/edit_channel_aclp
…e/edit_channel_aclp
Cloud Manager UI test results🔺 1 failing test on test run #6 ↗︎
Details
TroubleshootingUse this command to re-run the failing tests: pnpm cy:run -s "cypress/e2e/core/cloudpulse/timerange-verification.spec.ts" |
|||||||||||||||||
|
Merging as there are enough approvals and failure is unrelated. |
Description 📝
Add edit feature for notification channels.
Changes 🔄
/alerts/notification-channels/edit/$channelIdwith lazy loadingfilterEditChannelFormValuesutility to transform form data to API payload formatScope 🚢
Upon production release, changes in this PR will be visible to:
Target release date 🗓️
13 jan 2026
Preview 📷
How to test 🧪
Verification steps
[Verify in mock env]
Type,Name, andRecipients.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 ✅