Skip to content

🐛 fix(console): switch to components->info() #2283

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 1 commit into
base: 1.x
Choose a base branch
from

Conversation

chrillep
Copy link

@chrillep chrillep commented Aug 20, 2025

components->line requires two arguments in Laravel 12, causing an ArgumentCountError with a single string. Using components->info preserves formatting and restores compatibility. The $this->line helper has a different API and is not interchangeable with components->line.

Line now expects at least two arguments in Laravel 12, causing an ArgumentCountError when called with one. Use info to preserve the intended output and restore command compatibility.
Copy link
Contributor

coderabbitai bot commented Aug 20, 2025

Walkthrough

Updated the AddonsDiscover console command to use info() instead of line() for per-addon discovery output. All processing logic, manifest building, iteration flow, final success message, and return value remain unchanged.

Changes

Cohort / File(s) Summary
Console command output method adjustment
packages/core/src/Console/Commands/AddonsDiscover.php
Switched per-addon discovery messages from line() to info(); no changes to logic, manifest build, iteration, or return value.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

vercel bot commented Aug 20, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
lunar-docs Ready Ready Preview Comment Aug 20, 2025 7:10pm

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
packages/core/src/Console/Commands/AddonsDiscover.php (1)

31-33: Optional: Drop the inner tag or use twoColumnDetail for cleaner formatting

If you don’t specifically need the package name highlighted separately, the inner … is redundant when calling components->info(). Consider simplifying:

-            $this->components->info("Discovered Addon: <info>{$package}</info>");
+            $this->components->info("Discovered Addon: {$package}");

Alternatively, if you want a consistent two-column look with the package name emphasized:

-            $this->components->info("Discovered Addon: <info>{$package}</info>");
+            $this->components->twoColumnDetail('Discovered Addon', "<info>{$package}</info>");
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ecb4b46 and 7472bb7.

📒 Files selected for processing (1)
  • packages/core/src/Console/Commands/AddonsDiscover.php (1 hunks)
🔇 Additional comments (1)
packages/core/src/Console/Commands/AddonsDiscover.php (1)

31-33: LGTM: Switching to components->info() correctly avoids Laravel 12 ArgumentCountError

Using components->info() here aligns with Laravel 12’s updated components API and matches the style already used for the final message on Line 35. Good fix.

@glennjacobs
Copy link
Contributor

@alecritson I don't think we've revisited the addons manifest for a good while. I don't think it's being used.

Guessing we left it in for when we did want to re-implement it?

@chrillep
Copy link
Author

chrillep commented Aug 20, 2025

@alecritson I don't think we've revisited the addons manifest for a good while. I don't think it's being used.

Guessing we left it in for when we did want to re-implement it?

to be fair i haven't checked the internals/usage of the command, i just ran it and it failed. So i fixed that :)

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