fix(lint): fixed lint

[waleedlatif1]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Security enhancement
• Performance improvement
• Code refactoring (no functional changes)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

Additional Information:

Any additional information, configuration or data that might be necessary to reproduce the issue or use the feature.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Jul 20, 2025 4:33am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Jul 20, 2025 4:33am

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to cc4c7cd.

Security Overview

• 🔎 Scanned files: 1 changed file(s)

Detected Code Changes

Change Type	Relevant files
Bug Fix	► lint     Fixed lint issues

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[greptile-apps]

Greptile Summary

This PR makes a very simple but important change by adding a newline character at the end of search-modal.tsx. This follows the common best practice in software development where files should end with a newline character. While this may seem like a minor change, it's important for maintaining code consistency and preventing issues when concatenating files or viewing them in terminals.

The change is purely related to code style and formatting, with no functional changes to the codebase.

PR Description Notes:

• The PR template has not been filled out properly - checkboxes for type of change and other sections are left unchecked
• No specific issue number is referenced

Confidence score: 5/5

1. This PR is extremely safe to merge as it only adds a newline character
2. The change is purely formatting-related with no impact on functionality
3. No files need additional attention as the change is straightforward and well-understood

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}