fix: clamp theme automation interval input

[mayurigade-hub]

Related Issue

Closes #323

---

Description

Fixed an issue where the Theme Automation interval input could display values outside the allowed range even though the backend automatically sanitized them.

Previously, if a user entered a value such as 999, the backend correctly clamped it to 120, but the input field continued to display 999. This caused the UI to become inconsistent with the actual saved configuration.

This fix clamps the interval value between 1 and 120 in settings.js and immediately updates the input field with the sanitized value before saving.

---

Changes Made

• Added client-side validation for the Theme Automation interval input.
• Clamped the parsed interval value to the valid range (1–120).
• Updated the input field to display the clamped value before saving.
• Ensured the UI always matches the value stored by the backend.

---

Steps to Test

1. Open Settings.
2. Enable Theme Automation.
3. Enter 999 in Check Interval (Minutes).
4. Click outside the input or trigger a save.
5. Verify the input automatically changes to 120.
6. Enter 0 and verify it changes to 1.
7. Enter a valid value such as 30 and verify it remains unchanged.
8. Confirm the saved setting matches the displayed value.

---

Expected Result

• The interval value is always clamped between 1 and 120.
• The input field displays the sanitized value immediately.
• The UI and saved configuration remain consistent.
• Valid values are saved without modification.

---

Files Changed

• settings.js

---

Type of Change

☑️ Bug fix

☐ New feature

☐ Breaking change

☐ Documentation update

[vercel]

@mayurigade-hub is attempting to deploy a commit to the Dot_NotSam's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 557afd0b-6d9c-40e7-b63b-0f5ae2a4dece

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[mayurigade-hub]

Hello @SamXop123
Please review this PR.
Thank you!

[github-actions]

🎉 Congratulations @mayurigade-hub! 🎉

Your pull request has been successfully merged into Paraline! Thank you so much for your valuable contribution and effort. Every single improvement helps make Paraline a better desktop experience for everyone! 🙌

🚀 What's Next?

• Keep the momentum going! Feel free to browse through our open Issues and grab another one that interests you!
• Support the Project: If you enjoyed contributing to Paraline, please take a second to star our repository! It helps increase the project's visibility and supports our community. ⭐

💬 Stay Connected:
Have any questions, want feedback, or just want to discuss further contributions? Feel free to reach out directly to the maintainer on Discord: dot_notsam!

Thank you again, and keep up the amazing work! 💻✨