Skip to content

Conversation

@2witstudios
Copy link
Owner

@2witstudios 2witstudios commented Feb 10, 2026

Summary

Removed the "Markdown supported" hint text from the channel input footer component.

Changes

  • Removed the markdown hint span element that displayed "Markdown supported" text in the channel input footer
  • This text was only visible on small screens and above (hidden on mobile via hidden sm:inline)

Rationale

The markdown hint appears to be redundant or no longer needed in the UI. This simplifies the footer layout and reduces visual clutter in the input area.

https://claude.ai/code/session_01FMzdzbsRtLZVMYjxSJd1R6

Summary by CodeRabbit

  • Style
    • Removed the "Markdown supported" hint from the channel input footer on larger screens.

Removed the markdown hint text that was displayed in the channel/DM input area footer.

https://claude.ai/code/session_01JQR9D8VPTGMFVJFVXKR5C21
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 10, 2026

📝 Walkthrough

Walkthrough

The PR removes the "Markdown supported" hint text from the ChannelInputFooter component, reducing visual clutter in the input area on larger screens without altering any functional behavior or logic.

Changes

Cohort / File(s) Summary
UI Refinement
apps/web/src/components/layout/middle-content/page-views/channel/ChannelInputFooter.tsx
Removed the "Markdown supported" hint text element from the right-attached controls area.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hint of markdown fades away,
The footer's cleaner now, hooray!
Five lines removed with gentle grace,
Simplicity wins the typing space! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately and specifically describes the main change: removing the Markdown hint from the channel input footer component.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude/remove-markdown-text-l5c21

No actionable comments were generated in the recent review. 🎉


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.

@2witstudios 2witstudios merged commit f26a6d5 into master Feb 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants