Skip to content

🎯 fix: Input validation to the product discount countdown timer percentage field#430

Merged
mrabbani merged 1 commit intodevelopfrom
fix/validation-to-the-product-countdown-timer-discount-percentage-field
Aug 27, 2025
Merged

🎯 fix: Input validation to the product discount countdown timer percentage field#430
mrabbani merged 1 commit intodevelopfrom
fix/validation-to-the-product-countdown-timer-discount-percentage-field

Conversation

@devAsadNur
Copy link
Contributor

@devAsadNur devAsadNur commented May 13, 2025

Summary by CodeRabbit

  • New Features
    • The product discount input now only accepts numeric values between 0 and 100 in the WooCommerce product data panel for the countdown timer module, improving data accuracy and user experience.

@devAsadNur devAsadNur self-assigned this May 13, 2025
@devAsadNur devAsadNur added Need Dev Review Label for developer review needs. Need Testing Label for qa testing labels May 13, 2025
@coderabbitai
Copy link

coderabbitai bot commented May 13, 2025

Walkthrough

The change updates the WooCommerce product data panel for the countdown timer module by modifying the discount input field. The input type is changed from text to number, and minimum and maximum constraints are set to 0 and 100, ensuring only valid percentage values can be entered.

Changes

File(s) Change Summary
Includes/Modules/CountdownTimer/templates/wc-product-data-panels.php Changed discount input from text to number type; added min/max constraints (0–100); updated array syntax.

Sequence Diagram(s)

sequenceDiagram
    participant Admin as Product Admin
    participant WCPanel as WooCommerce Product Data Panel

    Admin->>WCPanel: Open product discount settings
    WCPanel->>Admin: Render discount input (type=number, min=0, max=100)
    Admin->>WCPanel: Enter discount value (validated client-side)
    WCPanel->>Admin: Prevent invalid input (non-numeric, <0, >100)
Loading

Assessment against linked issues

Objective Addressed Explanation
Input validation prevents entering percentages above 100% (#68)
Negative values are rejected with appropriate error messages (#68)
Non-numeric characters are prevented or cleaned from input (#68)
User receives clear feedback when entering invalid values (#68) No evidence of user feedback or error messaging in the code change.
Validation occurs both client-side and server-side (#68) Only input type and constraints changed; no server-side validation logic observed.

Poem

Oh, what a hop for the countdown clock,
Now discounts stay between zero and a hundred—what a shock!
No more wild numbers, no sneaky text,
Just tidy input, as bunnies expect.
With paws on the keys, we keep things right—
Hooray for clean fields, and discounts polite!
🐰✨

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@devAsadNur devAsadNur requested a review from mrabbani May 13, 2025 09:31
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
Includes/Modules/CountdownTimer/templates/wc-product-data-panels.php (1)

19-33: Excellent improvement to input validation!

The changes effectively implement proper input validation for the discount percentage field by:

  1. Changing the input type to 'number'
  2. Setting minimum and maximum constraints (0-100)
  3. Modernizing the array syntax from array() to []

These changes directly address the issue mentioned in #68 and will prevent users from entering invalid discount percentages.

Consider also adding a step attribute to control the decimal precision, if decimal percentages are allowed:

'custom_attributes' => [
        'min' => '0',
        'max' => '100',
+       'step' => '0.01',
],
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 59550f2 and dd46213.

📒 Files selected for processing (1)
  • Includes/Modules/CountdownTimer/templates/wc-product-data-panels.php (1 hunks)

@devAsadNur devAsadNur changed the title 🎯 fix: Input validation to the product countdown timer discount percentage field 🎯 fix: Input validation to the product discount countdown timer percentage field May 15, 2025
@mrabbani mrabbani merged commit 4e0a89d into develop Aug 27, 2025
@mrabbani mrabbani deleted the fix/validation-to-the-product-countdown-timer-discount-percentage-field branch September 12, 2025 03:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Need Dev Review Label for developer review needs. Need Testing Label for qa testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants