-
Notifications
You must be signed in to change notification settings - Fork 61
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
feat(web): Organization search - different placeholder #17014
feat(web): Organization search - different placeholder #17014
Conversation
WalkthroughThe changes in this pull request introduce a new optional property, Changes
Possibly related PRs
Suggested labels
Suggested reviewers
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
Documentation and Community
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #17014 +/- ##
========================================
Coverage 35.59% 35.59%
========================================
Files 6924 6923 -1
Lines 146382 146235 -147
Branches 41560 41539 -21
========================================
- Hits 52100 52058 -42
+ Misses 94282 94177 -105
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 51 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
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
🧹 Outside diff range and nitpick comments (2)
apps/web/components/Header/Header.tsx (1)
Line range hint
35-100
: Consider documenting the new feature in component documentationThe implementation is clean and follows best practices. To improve maintainability, consider:
- Adding JSDoc comments for the new
searchPlaceholder
prop to document its purpose and usage- Updating any relevant component documentation or storybook examples
apps/web/layouts/main.tsx (1)
408-415
: LGTM! Consider simplifying the placeholder text assignment.The implementation correctly handles localization and follows TypeScript best practices. However, the default placeholder text could be simplified.
Consider this more concise approach:
searchPlaceholder={ organizationSearchFilter - ? n( - 'organizationPageSearchPlaceholder', - activeLocale === 'is' ? 'Leita' : 'Search', - ) + ? n('organizationPageSearchPlaceholder', activeLocale === 'is' ? 'Leita' : 'Search') : undefined }
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (2)
apps/web/components/Header/Header.tsx
(3 hunks)apps/web/layouts/main.tsx
(1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
apps/web/components/Header/Header.tsx (1)
Pattern apps/**/*
: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/web/layouts/main.tsx (1)
Pattern apps/**/*
: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
🔇 Additional comments (3)
apps/web/components/Header/Header.tsx (3)
35-35
: LGTM! Property addition follows TypeScript best practices
The new optional searchPlaceholder
property is well-typed and follows the existing interface structure.
47-47
: LGTM! Props destructuring is clean and consistent
The searchPlaceholder
prop is correctly destructured and follows the component's existing patterns.
100-100
: LGTM! Placeholder fallback logic is well implemented
The use of the nullish coalescing operator with translation fallback maintains proper internationalization support while allowing custom placeholders.
Datadog ReportBranch report: ✅ 0 Failed, 84 Passed, 0 Skipped, 25.13s Total Time |
* Add different placeholder * Add namespace check --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Organization search - different placeholder
Show different placeholder on organization pages for the search at the top
Before
After
Checklist:
Summary by CodeRabbit
searchPlaceholder
property for the search input in the Header component, enhancing user experience by allowing personalized placeholder text based on context.searchPlaceholder
property in the Header component.