-
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: [DI-22558] - Added Trigger condition and Dimension Filter components #11445
upcoming: [DI-22558] - Added Trigger condition and Dimension Filter components #11445
Conversation
…n for error validation and minor changes
…es in validation schema
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.
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/DimensionFilter.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/DimensionFilterField.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/DimensionFilterField.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/DimensionFilterField.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/DimensionFilterField.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/DimensionFilterField.tsx
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/TriggerConditions.tsx
Outdated
Show resolved
Hide resolved
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/Criteria/TriggerConditions.tsx
Outdated
Show resolved
Hide resolved
#11445 (review), @jaalah-akamai , from what I remember for the Metric discussions, I had informed about these issues for the screens like Ipad or tablet like screens when they are in potrait mode. I will see to the UX changes. |
@jaalah-akamai , For the re-renderings issue we also not sure what's causing this behaviour. From our observations it is re-rendering entire page when we clear an option or we choose CPU utilization. Not sure what's causing this behavior |
I believe that re-render is happening because of the |
@bnussman-akamai, #11445 (comment) as per this, in this particular situation is it okay for the form to re-render just for that one field ? As we do want to pass it through the top-level component. |
… to the component
FormContext may be an option here and we could just remove that field from the payload, but this can be an optimization we make maybe with your UX changes. |
@jaalah-akamai , The UX changes have been pushed. The units are still overloading in some situations, but there is plan to use them as adornments with using a shortened form for the units. That will be pursued as an enhancement once all the features are done. Regarding the error validation resolution, I'm not able to pinpoint why the issue is happening and requesting if there was a similar behaviour before with |
…ic Data Field and Dimension Filter Data Field
34d575b
to
e364d1d
Compare
…d of exporting to fix the failing tests
Coverage Report: ❌ |
fb29615
to
f20078a
Compare
…osh_type_fixes
Merge latest linode develop and type changes
…rs-and-trigger-conditions
Cloud Manager UI test results🎉 471 passing tests on test run #18 ↗︎
|
…omponents (linode#11445) * upcoming: [DI-22558] - Added Trigger condition and Dimension Filter changes * removed unnecessary console log statement * upcoming: [DI-22558] - Importing right interface for Trigger condition for error validation and minor changes * upcoming: [DI-22588] - Added the Unit Tests for the components * upcoming: [DI-22588] - Added changesets and few changes to the messages in validation schema * upcoming: [DI-22588] - Review comments and made some minor UX changes to the component * Updated stylings * upcoming: [DI-22588] - UX changes * upcoming: [DI-22588] - Fixed the validation error resolution for Metric Data Field and Dimension Filter Data Field * upcoming: [DI-22588] - Review changes * upcoming: [DI-22588] - Moved mockData to individual test files instead of exporting to fix the failing tests * upcoming: [DI-22558] - Typescript issue fixes * Update constants.ts --------- Co-authored-by: nikhagra-akamai <nagrawal@akamai.com> Co-authored-by: vmangalr <vmangalr@akamai.com> Co-authored-by: venkatmano-akamai <chk-Venkatesh@outlook.com>
Description 📝
Changes 🔄
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 📷
How to test 🧪
Prerequisites
(How to setup test environment)
The tabs are controlled by a featureFlag called aclpAlerting, the flag has been currently disabled. For testing enable the definitions part of the aclpAlerting flag to be true.
The API endpoints are not live yet, so use Legacy MSW Handlers for the mock responses
In Monitor (once the prerequisites are followed) , Alerts tab should be visible next to Dashboards.
Under that, Definition tab and a Create button should be visible.
On clicking Create, the Form Page should be visible
To choose from the Data Field drop down, selecting a Service is required
Verification steps
(How to verify changes)
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 ✅