-
Notifications
You must be signed in to change notification settings - Fork 519
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
Fix : Filter badges visibility in resource page on selecting same date #10002
base: develop
Are you sure you want to change the base?
Conversation
WalkthroughThe pull request modifies the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for care-ohc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/hooks/useFilters.tsx (1)
132-136
: Document the special handling of equal range values.Consider adding a comment to explain why equal range values are handled differently. This will help future maintainers understand the rationale behind this behavior.
if (values[0] === values[1]) + // When min and max values are equal (e.g., same date selected), + // treat it as a single filter instead of a range to prevent duplicate badges return [{ name, value: values[0], paramKey: paramKeys[0] }];
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/hooks/useFilters.tsx
(1 hunks)
🔇 Additional comments (1)
src/hooks/useFilters.tsx (1)
133-133
: LGTM! The fix correctly handles equal range values.The change fixes the badge visibility issue by treating equal min/max values as a single filter parameter instead of a range. This is the correct behavior as it prevents duplicate badges when the same date is selected.
However, to prevent future regressions, consider adding test cases for:
- Range with equal values (e.g., same date)
- Range with different values
- Edge cases (e.g., undefined values)
Would you like me to help generate the test cases?
Proposed Changes
@ohcnetwork/care-fe-code-reviewers
Merge Checklist
Summary by CodeRabbit