-
-
Notifications
You must be signed in to change notification settings - Fork 84
refactor: migrate to functional nixopus-cli #625
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
Conversation
|
Caution Review failedThe pull request is closed. WalkthroughExtensive CLI refactoring removes class-based command implementations (preflight, clone, conflict, conf, service, proxy, test) and replaces them with modular, function-based utilities. The install command is enhanced with external database URL and staging parameters, while utilities are restructured from monolithic classes to stateless functions. Docker compose files and versioning are updated accordingly. Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60–90 minutes Areas requiring extra attention:
Possibly related PRs
Poem
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (81)
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. Comment |
* feat: add support for external database connectivity * fix: argument not passed ot install class * fix: argument not passed ot install class * feat: makes use of the docker compose prod file even during custom repo and branches * fix: converts ipv6 database to ipv4 * fix: prepared statement error for supabase db connection
Co-authored-by: Raghavendra Bhat <[email protected]>
Issue
Link to related issue(s):
Description
Short summary of what this PR changes or introduces.
Scope of Change
Select all applicable areas impacted by this PR:
Screenshot / Video / GIF (if applicable)
Attach or embed screenshots, screen recordings, or GIFs demonstrating the feature or fix.
Related PRs (if any)
Link any related or dependent PRs across repos.
Additional Notes for Reviewers (optional)
Anything reviewers should know before testing or merging (e.g., environment variables, setup steps).
Developer Checklist
To be completed by the developer who raised the PR.
Reviewer Checklist
To be completed by the reviewer before merge.
Summary by CodeRabbit
Release Notes
Bug Fixes
Improvements
Chores
✏️ Tip: You can customize this high-level summary in your review settings.