-
Notifications
You must be signed in to change notification settings - Fork 366
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-21694] - Added Resource Select component to the Create-alert form #11331
upcoming: [DI-21694] - Added Resource Select component to the Create-alert form #11331
Conversation
…hat, converted few variables from snake case to camel case
'severity', | ||
]); | ||
// severity has a need for null in the form for edge-cases, so null-checking and returning it as an appropriate type | ||
const severity = formValues.severity!; | ||
return { ...values, severity }; | ||
const resourceIds = formValues.resource_ids!; |
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.
Adding resourceIds here as resource_ids are optional as per the API-spec. Using FieldPathByValue
on an optional property makes the name
prop a never
type in the ResourceMultiSelect
component. cc: @bnussman-akamai , @jaalah-akamai
…d case for few variables and properties
As discussed with @jaalah-akamai , The properties that use snake_case right now are the the ones used for the API so haven't changed them to camelCase. |
Coverage Report: ✅ |
textFieldProps={{ | ||
InputProps: { | ||
sx: { | ||
maxHeight: '60px', | ||
overflow: 'auto', | ||
}, | ||
}, | ||
}} |
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 know we did this for the dashboard filters since that design/layout was a little different. For the alerts, let's omit this and let it grow naturally. I've spoke with UX and we're in the process of coming up with a standard of how to address this, but the overflow UX is really poor and I don't think it's something we should be propagating
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.
Okay, removed that styling.
…sourceMultiSelect and modified and added few properties for the Alert interfaces as per the latest API-spec
packages/manager/src/features/CloudPulse/Alerts/CreateAlert/CreateAlertDefinition.tsx
Outdated
Show resolved
Hide resolved
...r/src/features/CloudPulse/Alerts/CreateAlert/GeneralInformation/ResourceMultiSelect.test.tsx
Outdated
Show resolved
Hide resolved
React.useEffect(() => { | ||
setValue(name, []); | ||
}, [region, serviceType, engine, setValue, name]); |
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.
React.useEffect(() => { | |
setValue(name, []); | |
}, [region, serviceType, engine, setValue, name]); |
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.
After discussing, it seems this is an actual side effect. We want the resources to reset if region, serviceType, or engine changes. cc: @bnussman-akamai thoughts?
We can keep this, this will eventually get replaced with an entirely different component once that work is done - we can revisit then
...anager/src/features/CloudPulse/Alerts/CreateAlert/GeneralInformation/ResourceMultiSelect.tsx
Show resolved
Hide resolved
…dynamic in the Unit Test, replaced the variable name from serviceWatcher to serviceTypeWatcher, added comment addressing need for useEffect()
/> | ||
), | ||
}); | ||
expect(getByLabelText('Cluster')); |
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.
will need to update this test depending on if label is changed to Clusters
^
and a small nitpick: if this test does need to be updated, could we also put a linebreak between each test while at it for better readability?
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.
whoops looks like I submitted this comment early - meant to include it as part of my below review
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.
Yeah @coliu-akamai , Clusters makes sense. I will make the changes and I'll add a linebreak too. Thank you for the approval
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.
…l to Clusters in case of Database service type
Cloud Manager UI test results🎉 455 passing tests on test run #5 ↗︎
|
Cloud Manager E2E Run #6896
Run Properties:
|
Project |
Cloud Manager E2E
|
Branch Review |
develop
|
Run status |
Failed #6896
|
Run duration | 35m 01s |
Commit |
0285c7a67f: upcoming: [DI-21694] - Added Resource Select component to the Create-alert form ...
|
Committer | santoshp210-akamai |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
3
|
Flaky |
6
|
Pending |
2
|
Skipped |
0
|
Passing |
459
|
View all changes introduced in this branch ↗︎ |
Tests for review
switch-linode-state.spec.ts • 1 failed test
Test | Artifacts | |
---|---|---|
switch linode state > reboots a linode from landing page |
Screenshots
Video
|
update-linode-labels.spec.ts • 1 failed test
Test | Artifacts | |
---|---|---|
update linode label > updates a linode label from details page |
Screenshots
Video
|
search-linodes.spec.ts • 1 failed test
Test | Artifacts | |
---|---|---|
Search Linodes > create a linode and make sure it shows up in the table and is searchable in main search tool |
Screenshots
Video
|
linodes/switch-linode-state.spec.ts • 1 flaky test
Test | Artifacts | |
---|---|---|
switch linode state > reboots a linode from details page |
Screenshots
Video
|
linodes/clone-linode.spec.ts • 1 flaky test
Test | Artifacts | |
---|---|---|
clone linode > can clone a Linode from Linode details page |
Screenshots
Video
|
linodes/update-linode-labels.spec.ts • 1 flaky test
Test | Artifacts | |
---|---|---|
update linode label > updates a linode label from the "Settings" tab |
Screenshots
Video
|
linodes/backup-linode.spec.ts • 1 flaky test
Test | Artifacts | |
---|---|---|
linode backups > can enable backups |
Screenshots
Video
|
kubernetes/lke-create.spec.ts • 1 flaky test
Test | Artifacts | |
---|---|---|
LKE Cluster Creation > can create an LKE cluster |
Screenshots
Video
|
The first 5 flaky specs are shown, see all 6 specs in Cypress Cloud.
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)
Verification steps
(How to verify changes)
Database
As an Author, I have considered 🤔
As an Author, before moving this PR from Draft to Open, I confirmed ✅