Skip to content

fix: opacity in email input bar#115

Merged
SatyamPandey-07 merged 1 commit into
niharika-mente:mainfrom
ShaikhGouhar:fix-opacity-issue
Jun 23, 2026
Merged

fix: opacity in email input bar#115
SatyamPandey-07 merged 1 commit into
niharika-mente:mainfrom
ShaikhGouhar:fix-opacity-issue

Conversation

@ShaikhGouhar

@ShaikhGouhar ShaikhGouhar commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Description

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

Fixes # (issue number)

Type of Change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

  • Manual testing (describe steps and browser tested in)

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code

Summary by CodeRabbit

  • Style
    • Minor formatting adjustment to styling configuration with no functional impact to user experience.

@vercel

vercel Bot commented Jun 20, 2026

Copy link
Copy Markdown

@ShaikhGouhar is attempting to deploy a commit to the niharika-mente's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

A trailing whitespace character is appended to the className string of the email <input> element in app/my-bookings/page.tsx. No Tailwind classes were added, removed, or reordered, and no logic or rendering behavior was changed.

Changes

Email Input className Whitespace

Layer / File(s) Summary
Email input className trailing space
app/my-bookings/page.tsx
A trailing space is added inside the className string on line 84; all existing Tailwind utility classes remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ⚠️ Warning The PR description is incomplete. While the template structure is followed, critical details are missing: no specific issue number is provided, no summary of the change is included, and the 'How Has This Been Tested?' section lacks implementation details. Complete the description by adding: (1) a specific issue number in 'Fixes #', (2) a clear summary of the opacity issue and the fix applied, (3) detailed testing steps and browser information, and (4) relevant motivation for the change.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'fix: opacity in email input bar' accurately describes the main change - adjusting the email input styling to fix an opacity issue.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@app/my-bookings/page.tsx`:
- Line 84: The trailing whitespace appended to the className attribute on the
email input element has no effect on styling and does not fix any opacity
issues. Remove the trailing whitespace at the end of the className string. If an
opacity adjustment is actually needed for the email input, add the appropriate
Tailwind opacity utility class (such as opacity-50, opacity-75, or similar) to
the className attribute alongside the existing utilities like w-full, px-4,
py-2.5, rounded-xl, border, border-gray-200, focus:outline-none, focus:ring-2,
focus:ring-blue-500, text-sm, and text-gray-900. Ensure the commit message
accurately reflects the actual styling change being made.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7b23d438-325e-4056-a1f8-c48f0b32567b

📥 Commits

Reviewing files that changed from the base of the PR and between 352b809 and 4929106.

📒 Files selected for processing (1)
  • app/my-bookings/page.tsx

Comment thread app/my-bookings/page.tsx

@TarunyaProgrammer TarunyaProgrammer left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fixes the email text visibility issue by explicitly setting text-gray-900 on the input field.

One suggestion: consider also setting bg-white on the input. The current fix ensures readable text, but on systems/browsers that apply dark-mode styles to form controls, a dark input background combined with dark text could create another contrast issue.

className="w-full px-4 py-2.5 rounded-xl border border-gray-200 focus:outline-none focus:ring-2 focus:ring-blue-500 text-sm text-gray-900 bg-white"

This would make the input appearance and contrast more consistent across environments.

@TarunyaProgrammer

Copy link
Copy Markdown
Collaborator

@ShaikhGouhar, is this pr supposed to solve #105 ??
You did'nt mention any issue to this!

@ShaikhGouhar

Copy link
Copy Markdown
Contributor Author

@ShaikhGouhar, is this pr supposed to solve #105 ?? You did'nt mention any issue to this!

yes, it was a visibility issue in searchbar input ,filters and email input but it seems that searchbar and filters issue is already solved so it is only for the visibility issue in email registration input

@SatyamPandey-07 SatyamPandey-07 merged commit f441352 into niharika-mente:main Jun 23, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Easy SSoC26 TO CONTRIBUTE

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants