-
Notifications
You must be signed in to change notification settings - Fork 105
chore: improve flag sorting logic in artisan commands #884
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
|
Warning Rate limit exceeded@almas1992 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 3 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughThe changes introduce modifications to the handling and display of command-line flags in the Changes
Suggested reviewers
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.50.
| Benchmark suite | Current: 9a8cd52 | Previous: 5779d21 | Ratio |
|---|---|---|---|
Benchmark_EncryptString |
6225 ns/op 2160 B/op 15 allocs/op |
2188 ns/op 2160 B/op 15 allocs/op |
2.85 |
Benchmark_EncryptString - ns/op |
6225 ns/op |
2188 ns/op |
2.85 |
Benchmark_DecryptString |
6125 ns/op 2040 B/op 17 allocs/op |
2083 ns/op 2040 B/op 17 allocs/op |
2.94 |
Benchmark_DecryptString - ns/op |
6125 ns/op |
2083 ns/op |
2.94 |
This comment was automatically generated by workflow using github-action-benchmark.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #884 +/- ##
==========================================
- Coverage 66.47% 66.42% -0.06%
==========================================
Files 151 151
Lines 10387 10376 -11
==========================================
- Hits 6905 6892 -13
- Misses 3124 3126 +2
Partials 358 358 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this 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
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
console/cli_helper.go(1 hunks)
🧰 Additional context used
🪛 GitHub Check: codecov/patch
console/cli_helper.go
[warning] 324-325: console/cli_helper.go#L324-L325
Added lines #L324 - L325 were not covered by tests
🔇 Additional comments (1)
console/cli_helper.go (1)
306-316: LGTM! Clear and well-structured initialization of built-in flags.The map of built-in flags and the helper function provide a clean way to identify built-in flags.
|
Unfortunately, in V2 we can’t access global options. But in V3(unreleased), they introduced the parent property, allowing subcommands to access flags from the top-level command.🙁 |
We could also hardcode it, although it’s not the best approach. |
hwbrzzl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Good catch, it's not a big deal. We can implement it in the future. |
hwbrzzl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great 👍



📑 Description
Ensures that built-in CLI flags are separated from user-defined flags, grouping them distinctly for better organization and clarity in the output.
Before:
After:
Closes https://github.com/goravel/goravel/issues/?
Summary by CodeRabbit
✅ Checks