Skip to content
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

Updated UX for ValueSetSelect component #9685

Merged
merged 8 commits into from
Jan 3, 2025

Conversation

abhimanyurajeesh
Copy link
Contributor

@abhimanyurajeesh abhimanyurajeesh commented Jan 3, 2025

Proposed Changes

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a new feature.
  • Update product documentation.
  • Ensure that UI text is kept in I18n files.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
  • Request for Peer Reviews
  • Completion of QA

Screenshot

image

Summary by CodeRabbit

  • New Features

    • Added localized messages for search functionality
      • "Searching..." indicator
      • Minimum character search prompt for search length under 3 characters
      • "No results found" message
  • Internationalization

    • Enhanced ValueSetSelect component with context-sensitive search feedback
    • Integrated translation support for search-related messages

@abhimanyurajeesh abhimanyurajeesh requested a review from a team as a code owner January 3, 2025 07:36
Copy link
Contributor

coderabbitai bot commented Jan 3, 2025

Walkthrough

The pull request updates the ValueSetSelect component to enhance user experience through internationalization support. The component now utilizes the useTranslation hook to provide localized feedback based on the search length and fetching state. Additionally, the English JSON locale file has been modified to reflect these changes, specifically updating the "searching" message to indicate an ongoing process.

Changes

File Change Summary
public/locale/en.json Updated "searching" value from "Searching" to "Searching..."
src/components/Questionnaire/ValueSetSelect.tsx - Removed noResultsMessage prop
- Integrated useTranslation hook
- Updated message display logic based on search length and fetching state

Assessment against linked issues

Objective Addressed Explanation
Improve UX for ValueSetSelect
Provide guidance for minimum search characters

Possibly related PRs

Suggested labels

needs testing, needs review

Suggested reviewers

  • Jacobjeevan

Poem

🐰 In the meadow, a search takes flight,
With messages clear, guiding the light.
Type three characters, and watch the fun,
"Searching..." we say, till the quest is done!
Hop along, dear friend, the path is bright! 🌟


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6363a58 and e79d2b2.

📒 Files selected for processing (2)
  • public/locale/en.json (1 hunks)
  • src/components/Questionnaire/ValueSetSelect.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • public/locale/en.json
  • src/components/Questionnaire/ValueSetSelect.tsx

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
🪧 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.
    • 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

Copy link

netlify bot commented Jan 3, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit e79d2b2
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67779c9d4a58160008dc3309
😎 Deploy Preview https://deploy-preview-9685--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.

Copy link
Contributor

@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)
src/components/Questionnaire/ValueSetSelect.tsx (1)

45-45: Consider localizing the placeholder text as well.

While the rest of the user-facing text is now internationalized, the placeholder = "Search..." string remains hardcoded in English. You can further enhance i18n coverage by moving it into the translation file.

-  placeholder = "Search...",
+  placeholder = t("valueSetSelect_placeholder"),
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ee27ecd and 6363a58.

📒 Files selected for processing (2)
  • public/locale/en.json (1 hunks)
  • src/components/Questionnaire/ValueSetSelect.tsx (3 hunks)
🔇 Additional comments (3)
src/components/Questionnaire/ValueSetSelect.tsx (2)

3-3: Good use of i18n for messaging.

Importing and using useTranslation is a clean approach to localize user-facing messages in the component.


86-92: Logical flow for conditional messages looks correct.

Contextual messaging based on search length, loading state, and empty results is clearly structured. This greatly improves user guidance during search operations.

public/locale/en.json (1)

1810-1812: Keys align well with component usage.

The newly added keys match perfectly with the conditional logic in ValueSetSelect.tsx.

@abhimanyurajeesh
Copy link
Contributor Author

@rithviknishad please look into it and let me if any changes required, thank you !

src/components/Questionnaire/ValueSetSelect.tsx Outdated Show resolved Hide resolved
src/components/Questionnaire/ValueSetSelect.tsx Outdated Show resolved Hide resolved
src/components/Questionnaire/ValueSetSelect.tsx Outdated Show resolved Hide resolved
@rithviknishad rithviknishad merged commit 0899ddf into ohcnetwork:develop Jan 3, 2025
21 checks passed
Copy link

github-actions bot commented Jan 3, 2025

@abhimanyurajeesh Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improving UX for ValueSetSelect component
2 participants