fix: [M3-10286] - Premature validation of Linode Alert numeric input

[pmakode-akamai]

Description 📝

Premature validation of the numeric inputs in the Linode alerts tab prevents the user from updating the value. The bug is at a Linode details page such as https://cloud.linode.com/linodes/:id/alerts

This field requires a non-null value, but in a text input the natural behavior is to either 1) select the entire current value and then hit delete/backspace, or 2) place the cursor at the end of the text string and then repeatedly hit backspace. Because this is a required field, a null value in the numeric input disables the toggle switch which then disables the numeric input that the user is attempting to edit.

If I want to change the text value from "180" to "90", i am required to update individual characters and never leave the input blank. The attached screenshot recording demonstrates the bug and the odd workaround that is necessary to replace the current value.  

Note

Addressing this in a follow-up PR

Screenshot

Changes 🔄

• Updated the behavior to allow numeric input fields to be temporarily cleared while editing, without disabling the field or defaulting the value to 0

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 🗓️

N/A

Preview 📷

Before	After
Screen.Recording.2025-08-04.at.1.03.18.PM.mov	Screen.Recording.2025-08-04.at.12.58.43.PM.mov

How to test 🧪

Reproduction steps

• Navigate to https://cloud.linode.com/linodes/:id/alerts
• Toggle on of the numeric inputs
• Use the delete key to clear the input
• Observe: the entire field has been disabled

Verification steps

• Go to https://cloud.linode.com/linodes/:id/alerts
• Clear a numeric input field (e.g., CPU alert) completely
• Ensure the toggle remains enabled while the input is empty
• Enter a new value (e.g., change 180 to 90) and confirm it's accepted
• Toggle the switch on/off and confirm it continues to work as expected
• Ensure entering 0 sets the toggle to the OFF state and keeps the input field disabled
• Save changes and verify the value persists

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

[dmcintyr-akamai]

can you create a subtask for tests?

[mjac0bs]

Thank you for fixing!

I'm pretty sure I'd observed this behavior before and noted as an existing issue, which is probably why you tagged me on this PR. 👍🏼

✅ Observed the bug, observed these changes address it, confirmed no console errors.

@pmakode-akamai re: the non-human-readable error messages for several of the fields - is this something we can submit to the API team for intake as a bug ticket?

[pmakode-akamai]

@pmakode-akamai re: the non-human-readable error messages for several of the fields - is this something we can submit to the API team for intake as a bug ticket?

Yes, I think we can. The non-human-readable error messages should ideally be more descriptive, and since this is an existing API issue, I'll go ahead and raise an ARB bug ticket for the API team.

Going to merge this PR so the issue remains reproducible and easy to reference.

EDIT: After taking another look, it looks like the validation issue is actually at the Linode Alerts object validation schema level in CM, not in the API 🤦🏻‍♂️. I'll open a quick follow-up PR to address it there.

Edit-2: Resolved validation message issue in PR: #12635

[pmakode-akamai]

can you create a subtask for tests?

@dmcintyr-akamai Created M3-10433 ✅

[linode-gh-bot]

Cloud Manager UI test results

🔺 3 failing tests on test run #3 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
3 Failing	702 Passing	4 Skipped	120m 37s

Details

Failing Tests
	Spec	Test
❌	linode-storage.spec.ts	Cloud Manager Cypress Tests→linode storage tab » delete disk
❌	qemu-reboot-upgrade-notice.spec.ts	Cloud Manager Cypress Tests→QEMU reboot upgrade notification » should display maintenance banner in 'Linode' landing page when one or more Linodes get impacted.
❌	object-storage-objects-multicluster.spec.ts	Cloud Manager Cypress Tests→Object Storage Multicluster objects » "before all" hook for "can upload, access, and delete objects"

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/linode-storage.spec.ts,cypress/e2e/core/notificationsAndEvents/qemu-reboot-upgrade-notice.spec.ts,cypress/e2e/core/objectStorageMulticluster/object-storage-objects-multicluster.spec.ts"