Skip to content

Conversation

@santoshp210-akamai
Copy link
Contributor

Description 📝

Covers the Overview and Settings section of the Notification Channel Show Details Page

Changes 🔄

List any change(s) relevant to the reviewer.

  • Create Detail, Overview, Recipients components
  • Relevant mocks and UTs

Scope 🚢

Upon production release, changes in this PR will be visible to:

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • No customers / Not applicable

Target release date 🗓️

Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

Preview 📷

Include a screenshot <img src="" /> or video <video src="" /> of the change.

🔒 Use the Mask Sensitive Data setting for security.

💡 For changes requiring multiple steps to validate, prefer a video for clarity.

FIGMA

image

localhost

Normal

Screenshot 2025-12-18 at 14 41 13

Usernames overflow use-case

Screen.Recording.2025-12-18.at.16.42.16.mov

How to test 🧪

Prerequisites

(How to setup test environment)

  • In Mock environment (Legacy MSW Handlers)
  • Enable the the notificationChannels in CloudPulse Alerting (aclpAlerting) to enable the mock feature flags
  • Under Monitor, click on Alerts. Click on the NotificationChannel Tab
  • In the list of Notification Channel, click on the Hyperlink-ed label , or go to the action item menu and choose show details

Reproduction steps

(How to reproduce the issue, if applicable)

  • ...
  • ...

Verification steps

(How to verify changes)

  • The Show details information reflects the mocked API data properly
  • The Recipients are scrollable when the recipients is more than the Box length
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


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All tests and CI checks are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

*/
channelId: number;
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

@santoshp210-akamai , do we need any changes in the file

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@venkymano-akamai , Idk why it was caught as a difference, but resolving conflicts fixed it.

Copy link
Contributor

@ankita-akamai ankita-akamai left a comment

Choose a reason for hiding this comment

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

LGTM

@github-project-automation github-project-automation bot moved this from Review to Approved in Cloud Manager Jan 16, 2026
@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🔺 1 failing test on test run #3 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
1 Failing864 Passing11 Skipped41m 35s

Details

Failing Tests
SpecTest
clone-linode.spec.tsCloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Approved

Development

Successfully merging this pull request may close these issues.

4 participants