8000 Renamed 'Errors' Tab to 'Console' and fixed console message coloring by robertheadley · Pull Request #3808 · RooCodeInc/Roo-Code · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Renamed 'Errors' Tab to 'Console' and fixed console message coloring #3808

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

robertheadley
Copy link
@robertheadley robertheadley commented May 22, 2025

Related GitHub Issue

Closes: #

Description

Renamed "Errors" Tab to "Console" in McpView.tsx
Updated view ID from 'errors-view' to 'console-view'
Changed empty state message to use 'noLogs' translation key
Fixed console message coloring in McpErrorRow.tsx

Test Procedure

Compiled and ran program. changes evident

Type of Change

  • 🐛 Bug Fix: Non-breaking change that fixes an issue.
  • New Feature: Non-breaking change that adds functionality.
  • 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
  • ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
  • 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
  • 📚 Documentation: Updates to documentation files.
  • ⚙️ Build/CI: Changes to the build process or CI configuration.
  • 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

  • Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
  • Scope: My changes are focused on the linked issue (one major feature/fix per PR).
  • Self-Review: I have performed a thorough self-review of my code.
  • Code Quality:
    • My code adheres to the project's style guidelines.
    • There are no new linting errors or warnings (npm run lint).
    • All debug code (e.g., console.log) has been removed.
  • Testing:
    • New and/or updated tests have been added to cover my changes.
    • All tests pass locally (npm test).
    • The application builds successfully with my changes.
  • Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
  • Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
  • Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
  • Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Before
image

After
443455488-e5a39fd4-3484-4bbd-b6af-277e9d71457b

Documentation Updates

Additional Notes

Get in Touch

robertheadley on discord


Important

Renamed "Errors" tab to "Console" and fixed console message coloring in McpView.tsx and McpErrorRow.tsx.

  • Renaming:
    • Renamed "Errors" tab to "Console" in McpView.tsx.
    • Updated view ID from errors-view to console-view.
    • Changed empty state message to use noLogs translation key.
  • Console Message Coloring:
    • Fixed message coloring in McpErrorRow.tsx by checking for stdout messages and setting appropriate colors.
    • Added logic to strip [STDOUT] prefix for cleaner display.
    • Added console logging for debugging message levels.

This description was created by Ellipsis for 2c0b2f1. You can customize this summary. It will automatically update as commits are pushed.

@robertheadley robertheadley marked this pull request as ready for review May 25, 2025 17:42
@robertheadley robertheadley requested review from mrubens and cte as code owners May 25, 2025 17:42
@@ -9,20 +9,55 @@ type McpErrorRowProps = {

export const McpErrorRow = ({ error }: McpErrorRowProps) => {
const color = useMemo(() => {
// Add debugging to log what level is coming in
console.log(`McpErrorRow level: ${error.level} for message: ${error.message.substring(0, 20)}...`)
Copy link

Choose a reason for hiding this comment

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

This debug log is helpful for development but should be removed or gated behind a debug flag before production.

Suggested change
console.log(`McpErrorRow level: ${error.level} for message: ${error.message.substring(0, 20)}...`)

@hannesrudolph hannesrudolph moved this from PR [Draft / In Progress] to TEMP in Roo Code Roadmap May 26, 2025
@daniel-lxs daniel-lxs moved this from TEMP to PR [Needs Review] in Roo Code Roadmap May 26, 2025
@hannesrudolph hannesrudolph moved this from PR [Needs Review] to TEMP in Roo Code Roadmap May 26, 2025
@hannesrudolph hannesrudolph moved this from TEMP to PR [Needs Review] in Roo Code Roadmap May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: PR [Needs Prelim Review]
Development

Successfully merging this pull request may close these issues.

2 participants
0