Repository navigation
Propagate --global to collection package installs - #277
Conversation
handleCollectionInstall never accepted or forwarded the global option, so `prpm install <collection> --global` installed every child package into project-local paths. Forward global (and eager on the auto-detected collection path, which also dropped it) to each child handleInstall, and add regression tests. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
🤖 My Senior Dev — Analysis Complete👤 For @khaliqgant📁 Expert in View your contributor analytics → 📊 3 files reviewed • 3 need attention
📚 Relevant Past Discussions:
🚀 Open Interactive Review →The full interface unlocks features not available in GitHub:
💬 Chat here: 📖 View all 12 personas & slash commandsYou can interact with me by mentioning In PR comments or on any line of code:
Slash commands:
AI Personas (mention to get their perspective):
For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews. |
CodeAnt Nitpicks1 code suggestion1. When a global child install fails, the surrounding catch treats the error as a collection lookup miss and falls through to
|
CodeAnt PR Risk: Low Risk
Assessed commit: |
User description
Summary
handleCollectionInstalldidn't accept aglobaloption, soprpm install <collection> --globalinstalled each child package into the project instead of globally.globaland passes it to every childhandleInstall. Both collection hand-offs ininstall.ts(thecollections/prefix and the auto-detected collection path) pass it through.eager; it now passes that too.Tests
collections.test.ts: every child getsglobal: truewhen the flag is set, and no child getsglobalwhen it isn't.tsc --noEmitis clean.🤖 Generated with Claude Code
CodeAnt-AI Description
Honor global and eager options when installing collections
What Changed
--globalnow installs every package in a collection to user-level locations instead of project-local paths.Impact
✅ Collection packages install globally when requested✅ Eager loading applies to auto-detected collections💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.