-
Notifications
You must be signed in to change notification settings - Fork 518
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: Facility Issues: Cover Not Functioning Properly and Minor Suggestions for the Facility Page #10021
base: develop
Are you sure you want to change the base?
FIX: Facility Issues: Cover Not Functioning Properly and Minor Suggestions for the Facility Page #10021
Conversation
WalkthroughThe pull request introduces enhancements to the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (7)
💤 Files with no reviewable changes (4)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms (1)
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/components/Facility/FacilityHome.tsx (1)
347-347
: Consider readability impact of text justification.While
text-justify
provides a clean look, it can create inconsistent word spacing and affect readability, especially for non-Latin scripts or when the text contains long words. Consider usingtext-left
for better readability across different languages and content types.-<CardContent className="mt-4 text-justify"> +<CardContent className="mt-4 text-left">
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
src/components/Common/AvatarEditModal.tsx
(6 hunks)src/components/Facility/FacilityHome.tsx
(5 hunks)
🔇 Additional comments (7)
src/components/Common/AvatarEditModal.tsx (4)
27-27
: LGTM! Well-structured prop addition.The new optional
hint
prop is properly typed asReact.ReactNode
, maintaining backward compatibility while allowing for flexible content.
55-55
: LGTM! Clean prop destructuring.The
hint
prop is properly destructured along with other props, maintaining consistent code style.
Line range hint
170-180
: LGTM! Clean implementation of customizable hints.The hint message implementation follows React best practices with a clear fallback pattern. The rename from
commonHint
todefaultHint
improves code clarity.
202-202
: LGTM! Consistent hint message placement.The hint message is consistently used in both the image preview and no-image states, providing clear guidance to users.
Also applies to: 253-253
src/components/Facility/FacilityHome.tsx (3)
212-212
: LGTM! Enhanced visual feedback.The gradient overlay transition provides smooth visual feedback on hover, improving the user experience.
239-239
: LGTM! Improved button visibility.The increased background opacity values provide better contrast while maintaining a consistent visual hierarchy in the hover states.
168-175
: Verify aspect ratio recommendation consistency.While the hint implementation is clean and well-internationalized, there's an inconsistency in the recommended aspect ratios:
- FacilityHome.tsx recommends 16:9
- AvatarEditModal's default hint recommends 1:1
This might confuse users if they see different recommendations in different contexts.
Co-authored-by: Rithvik Nishad <rithvikn2001@gmail.com>
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.
lgtm; just minor suggestion
{t("max_size_for_image_uploaded_should_be")} 1mb. | ||
<br /> | ||
{t("allowed_formats_are")} jpg,png,jpeg.{" "} | ||
{t("recommended_aspect_ratio_for")} the image is 16:9 |
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.
i don't think mixing english with translation language is a good idea. pass it as variables. check how to pass variables to i18n's t function and other existing usages
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.
Ya even I thought of doing that, since code was already existing, I didn't wanna do that but If this t
is not use anywhere else update it or else create a new one.
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.
update it; update it in existing ones too if any;
No worries 😉 let's do that minor suggestion. |
…cilityHome components
…anyurajeesh/care_fe into issues/10018/facility-page
Proposed Changes
Summary by CodeRabbit
New Features
AvatarEditModal
for customizable image upload guidanceStyle
MapPin
vertical spacing@ohcnetwork/care-fe-code-reviewers
Merge Checklist
Summary by CodeRabbit
New Features
Style
Localization