refactor(useCounter): Extract validateValue function and optimize performance

[wo-o29]

Overview

This PR refactors the useCounter hook by extracting the validateValue function outside the hook and removing unnecessary memoization to improve performance and code maintainability.

Reason for Change

The previous implementation had several inefficiencies:

1. Unnecessary memoization overhead: The validateValue function was wrapped with useCallback and then memoized again, creating unnecessary computational overhead
2. Memory inefficiency: Each hook instance created its own validateValue function, leading to redundant function creation
3. Complex dependency chain: The memoized validation function created an indirect dependency chain that was harder to track

Changes Made

• Extracted validateValue function outside the hook as a pure function
• Removed unnecessary useCallback for validation logic
• Simplified dependency arrays by directly depending on [min, max]
• Improved type safety with Omit<UseCounterOptions, 'step'>
• Enhanced code readability and maintainability

Checklist

• Did you write the test code?
• Have you run yarn run fix to format and lint the code and docs?
• Have you run yarn run test:coverage to make sure there is no uncovered line?
• Did you write the JSDoc?

[Copilot]

Pull Request Overview

This PR refactors the useCounter hook to optimize performance and improve code maintainability by extracting the validateValue function and removing unnecessary memoization.

• Extracts validateValue as a pure function outside the hook.
• Removes redundant useCallback usage and simplifies dependency arrays.
• Enhances type safety and clarity of the hook's logic.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (5bdb4ff) to head (b58b311).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #259   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           37        37           
  Lines         1093      1091    -2     
  Branches       324       326    +2     
=========================================
- Hits          1093      1091    -2     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kimyouknow]

Hi @wo-o29, thank you for your contribution!

After careful review, we've decided to close this PR. The refactoring (extracting validateValue and removing useCallback) doesn't provide a meaningful improvement over the current implementation:

1. useCallback removal: The current useCallback clearly signals memoization intent. Removing it doesn't improve performance but reduces semantic clarity.
2. Function extraction: validateValue is only used within the hook — moving it outside doesn't enable reuse, and makes the internal logic flow harder to follow.
3. Dependency array change: [validateValueMemoized] → [min, max] — functionally equivalent but the original is more self-documenting.

The existing code is already clean and maintainable. We appreciate your effort to optimize, but in this case the current approach is preferable.

If you'd like to contribute in other areas (new features, bug fixes), we'd love to have your help! Thank you.

[kimyouknow]

To clarify — I initially closed several PRs during a batch cleanup, but realized this one is a valid improvement. The concerns I mentioned were more about scope than code quality. Happy to merge after rebase + changeset!