ohcnetwork / care_fe

Care is a Digital Public Good enabling TeleICU & Decentralised Administration of Healthcare Capacity across States.
https://care.ohc.network
MIT License
255 stars 441 forks source link

Adjusted the view change button position #9172

Open nithish1018 opened 1 day ago

nithish1018 commented 1 day ago

Proposed Changes

Screen Recording:

https://github.com/user-attachments/assets/c6dbf3db-25bb-45a7-b3da-d61917797fd3

image

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

Summary by CodeRabbit

Summary by CodeRabbit

coderabbitai[bot] commented 1 day ago

Walkthrough

The changes in this pull request involve modifications to the ListView components in both ResourceList.tsx and ShiftingList.tsx. Key updates include the enhancement of internationalization support for the title in the Resource List and the reinstatement of the AdvancedFilterButton in both components. The overall structure, logic, and functionality of the components remain unchanged, ensuring consistent data handling and user experience.

Changes

File Path Change Summary
src/components/Resource/ResourceList.tsx Updated title prop to use translatable string; reinstated AdvancedFilterButton.
src/components/Shifting/ShiftingList.tsx Reintroduced AdvancedFilterButton in JSX; minor formatting adjustments.
src/components/Common/SortDropdown.tsx Updated containerClassName property of DropdownMenu to include z-20.

Assessment against linked issues

Objective Addressed Explanation
Button position consistency across views (#9170) βœ…
Search icon overlay issue in dropdown (#9174) ❌ No changes made to address the overlay issue.

Possibly related PRs

Suggested labels

tested

Suggested reviewers

πŸ‡ In the meadow, where the bunnies play,
A button's place, now here to stay.
With titles that dance in many a tongue,
Our filters are back, let the joy be sung!
Hopping along, we fix and we cheer,
Consistent views, bring the friends near! 🐰✨

[!WARNING]

Rate limit exceeded

@nithish1018 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 53 seconds before requesting another review.

βŒ› How to resolve this issue? After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.
🚦 How do rate limits work? CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information.
πŸ“₯ Commits Reviewing files that changed from the base of the PR and between 3ecad4f318591f7b44f481533afcec78dd75e693 and dfc7255dc3bbfadeacc6e23f32e590d22d0c2d9d.

[!WARNING] There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

πŸ”§ eslint > If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.
src/components/Common/SortDropdown.tsx Oops! Something went wrong! :( ESLint: 8.57.1 Error: Failed to load parser '@typescript-eslint/parser' declared in '.eslintrc.json': Cannot find module '@typescript-eslint/parser' Require stack: - /.eslintrc.json at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15) at Function.resolve (node:internal/modules/helpers:145:19) at Object.resolve (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2346:46) at ConfigArrayFactory._loadParser (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3325:39) at ConfigArrayFactory._normalizeObjectConfigDataBody (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3099:43) at _normalizeObjectConfigDataBody.next () at ConfigArrayFactory._normalizeObjectConfigData (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3040:20) at _normalizeObjectConfigData.next () at ConfigArrayFactory.loadInDirectory (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2886:28) at CascadingConfigArrayFactory._loadConfigInAncestors (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3871:46)

πŸ“œ Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
πŸ“₯ Commits Reviewing files that changed from the base of the PR and between 3ecad4f318591f7b44f481533afcec78dd75e693 and dfc7255dc3bbfadeacc6e23f32e590d22d0c2d9d.
πŸ“’ Files selected for processing (1) * `src/components/Common/SortDropdown.tsx` (1 hunks)
πŸ”‡ Additional comments (1)
src/components/Common/SortDropdown.tsx (1) `30-30`: **LGTM! This change addresses the search icon overlay issue.** The addition of `z-20` to the container className should resolve the issue where the search icon was overlaying the dropdown menu cards in the Sort By menu. Let's verify there are no conflicting z-index values that might affect this fix:
βœ… Verification successful **Z-index value of 20 is appropriate and doesn't conflict with overlapping components** Based on the z-index analysis: - The z-20 value aligns well with the application's z-index hierarchy: - Regular content/components: z-0 to z-10 - Dropdowns/sticky elements: z-20 to z-30 - Modals/overlays/tooltips: z-40 to z-50 The chosen z-20 for the sort dropdown: - Is higher than the search icon (z-10) which fixes the overlay issue - Matches other dropdown menus in the codebase - Stays below modal overlays and tooltips - Maintains consistent z-index patterns across the application
🏁 Scripts executed The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Description: Check for potential z-index conflicts in the codebase # Look for other components that might overlap with our z-20 dropdown # Search for z-index classes in tsx/jsx files echo "Checking for z-index usage in components:" rg -g '*.tsx' -g '*.jsx' 'z-(\d+|auto)' --no-filename | sort | uniq # Search for explicit z-index style properties echo -e "\nChecking for inline z-index styles:" ast-grep --pattern 'style={$_zIndex: $_}' ``` Length of output: 7386

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?

❀️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
πŸͺ§ Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `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 generate unit testing code for this file.` - `@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 generate unit testing code.` - `@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.` 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
netlify[bot] commented 1 day ago

Deploy Preview for care-ohc ready!

Name Link
Latest commit dfc7255dc3bbfadeacc6e23f32e590d22d0c2d9d
Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/673f13d75dcffd0008987332
Deploy Preview https://deploy-preview-9172--care-ohc.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.