Skip to content
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

perf: fixed issues with argument handling, command lookup & file pro… #23574

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

0xkazak
Copy link

@0xkazak 0xkazak commented Feb 2, 2025

Description

This PR addresses several issues in the script to ensure better functionality and compatibility.

Key changes include:

  • Improved argument handling in f_exit_success: Fixed how arguments are passed to f_echo_stderr and ensured exit 0 works correctly after output.
  • Replaced which with command -v: Switched from which to command -v for better compatibility and reliability.
  • Fixed check for STAGED_GO_FILES: Improved the check to handle cases where the variable might contain spaces or be empty.
  • Quoted variables for safety: Ensured variables are properly quoted to handle filenames with spaces.
  • Corrected .pb.go regex: Updated regex to match only files ending with .pb.go and avoid false positives.

These changes make the script more robust and prevent errors related to file handling and command lookup.


Author Checklist

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Chores

    • Enhanced the automated validation process to handle inputs more reliably.
  • Bug Fixes

    • Improved command detection and error messaging, reducing false alerts during code submissions.

Copy link
Contributor

coderabbitai bot commented Feb 2, 2025

📝 Walkthrough

Walkthrough

The pre-commit hook script has been updated to improve its robustness and clarity. Modifications include enhanced quoting for handling special characters, improved conditional checks using idiomatic Bash patterns, and a more reliable command presence check using command -v instead of which. Additionally, the regex used for matching .pb.go file patterns was refined and command execution now quotes file names to safely handle spaces and special characters.

Changes

File(s) Change Summary
contrib/githooks/pre-commit • Updated f_echo_stderr to use double quotes for its arguments.
• Modified f_exit_success to use [[ -n "$*" ]] for checking passed arguments.
• Replaced which with command -v in f_check_cmds with clearer error messages.
• Changed conditional checks for STAGED_GO_FILES to use [[ -n "$STAGED_GO_FILES" ]].
• Refined regex to correctly match .pb.go files by appending $.
• Ensured file variables are quoted when invoking gofmt, misspell, and goimports.

Sequence Diagram(s)

sequenceDiagram
    participant Script as Pre-commit Hook
    participant Checker as f_check_cmds
    participant Processor as File Processor
    participant Formatter as Tools (gofmt, misspell, goimports)
    
    Script->>Checker: Validate required commands using "command -v"
    Checker-->>Script: Return command availability status
    Script->>Script: Check if STAGED_GO_FILES exists using [[ -n ]]
    Script->>Processor: Loop over each staged file
    Processor->>Processor: Verify file pattern (.pb.go$) using refined regex
    Processor->>Formatter: Execute formatting commands with quoted filenames
    Formatter-->>Processor: Return command output
    Processor-->>Script: File processing complete
    Script->>Script: Evaluate overall exit status with f_exit_success
Loading

Suggested labels

C:CLI

Suggested reviewers

  • kocubinski
  • julienrbrt
  • auricom

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?

❤️ 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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.

Documentation and Community

  • 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
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: 0

🧹 Nitpick comments (4)
contrib/githooks/pre-commit (4)

8-10: Consider using printf for better format control.

While the current implementation is safer with quoted arguments, using printf would provide better control over output formatting and special character handling.

-  echo "$@" >&2
+  printf '%s\n' "$@" >&2

20-26: LGTM! More reliable command checking.

The change to use command -v instead of which is a significant improvement as it's more reliable and POSIX compliant. The variable quoting also enhances safety.

Consider enhancing the error message to be more informative:

-      f_exit_success "Couldn't find '$cmd', skipping"
+      f_exit_success "Required command '$cmd' not found. Please install it to enable pre-commit checks."

32-35: Consider adding file existence checks.

While the script handles file patterns correctly, it would be more robust to verify file existence before processing.

 for file in $STAGED_GO_FILES; do
+    if [[ ! -f "$file" ]]; then
+        f_echo_stderr "Warning: '$file' not found, skipping"
+        continue
+    fi
     if [[ "$file" =~ vendor/ ]] || [[ "$file" =~ tests/mocks/ ]] || [[ "$file" =~ \.pb\.go$ ]]; then

37-41: LGTM! Safer command execution.

The addition of quotes around "$file" in all commands ensures safe handling of filenames with spaces or special characters.

Consider adding error handling for the git add command:

-    git add "$file"
+    if ! git add "$file"; then
+        f_echo_stderr "Warning: Failed to stage changes for '$file'"
+    fi
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9a92843 and 30f7ba6.

📒 Files selected for processing (1)
  • contrib/githooks/pre-commit (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Summary
🔇 Additional comments (2)
contrib/githooks/pre-commit (2)

12-18: LGTM! Improved argument handling.

The change to use [[ -n "$*" ]] is a more idiomatic way to check for non-empty arguments in bash. The function correctly handles the exit status and argument passing.


30-31: LGTM! Better empty check.

The change to use [[ -n "$STAGED_GO_FILES" ]] is a more idiomatic way to check for non-empty strings in bash.

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.

1 participant