-
Notifications
You must be signed in to change notification settings - Fork 324
Fix 1150 evaluation notes limit #1450
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
Merged
Sachinchaurasiya360
merged 7 commits into
Sachinchaurasiya360:main
from
mayank200529:fix-1150-evaluation-notes-limit
Jun 6, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
58f4001
fix(opensource): trim search query before database lookup
mayank200529 fe036cf
fix: trim search query before database lookup
mayank200529 1f70cc4
chore: resolve opensource routes conflict
mayank200529 88d06df
fix: use trimmed search value in filters
mayank200529 88fdf1b
chore: resolve merge conflicts
mayank200529 b262571
fix: resolve merge conflicts
mayank200529 13895fd
fix(recruiter): add notes character limit and counter
mayank200529 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Remove the BOM (Byte Order Mark) character from the import statement.
The first line contains an invisible BOM character (U+FEFF) before the
importkeyword, which can cause module parsing failures and unexpected syntax errors in Node.js ES modules.🧹 Proposed fix to remove BOM
Note: Most editors display BOM invisibly. To fix: delete the entire first line and retype it, or use a tool like
dos2unixor your editor's "Remove BOM" feature.📝 Committable suggestion
🤖 Prompt for AI Agents