Skip to content
This repository was archived by the owner on Jan 23, 2026. It is now read-only.

Need to use the changed directory when using last known project#358

Merged
jhaynie merged 1 commit intomainfrom
change-dir
May 28, 2025
Merged

Need to use the changed directory when using last known project#358
jhaynie merged 1 commit intomainfrom
change-dir

Conversation

@jhaynie
Copy link
Copy Markdown
Member

@jhaynie jhaynie commented May 28, 2025

this can have the effect of using one directory for bundle and another for deploy which can cause a mismatch

Summary by CodeRabbit

  • Bug Fixes
    • Ensured the app automatically switches to the last used project directory if the current one is not found, improving reliability when accessing projects.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 28, 2025

Walkthrough

The ResolveProjectDir function in internal/project/project.go was updated to change the process's current working directory to the last used project directory (from preferences) if the project directory is not found in the current or specified directory but is found in preferences.

Changes

File(s) Change Summary
internal/project/project.go ResolveProjectDir now calls os.Chdir(dir) when resolving to the last used project directory.

Poem

A hop to the past, a leap to the right,
The project path lost, but now in plain sight.
With one little Chdir, we’re back on our way,
The rabbit finds home—no more delay!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

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

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

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

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.

@jhaynie jhaynie merged commit 5b13734 into main May 28, 2025
13 of 14 checks passed
@jhaynie jhaynie deleted the change-dir branch May 28, 2025 15:58
Copy link
Copy Markdown
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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 139c37c and 0b2062c.

📒 Files selected for processing (1)
  • internal/project/project.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Test CLI Upgrade Path (windows-latest)
  • GitHub Check: Build and Test (macos-latest)
  • GitHub Check: Analyze (go)

dir = viper.GetString("preferences.project_dir")
if ProjectExists(dir) {
tui.ShowWarning("Using your last used project directory (%s). You should change into the correct directory or use the --dir flag.", dir)
os.Chdir(dir)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

Add error handling for the directory change operation.

The os.Chdir(dir) call can fail for various reasons (directory doesn't exist, permission issues, etc.) but the error is not being handled. This could lead to silent failures where the function returns successfully but the working directory change didn't actually occur.

Apply this diff to add proper error handling:

-			os.Chdir(dir)
+			if err := os.Chdir(dir); err != nil {
+				logger.Warn("Failed to change to project directory %s: %v", dir, err)
+				tui.ShowBanner("Directory Change Failed", fmt.Sprintf("Could not change to the project directory %s: %v\n\nPlease navigate to the directory manually or use the --dir flag.", dir, err), false)
+				os.Exit(1)
+			}

Additionally, consider documenting this side effect in the function's documentation since changing the working directory affects the entire process and could have implications for callers.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
os.Chdir(dir)
if err := os.Chdir(dir); err != nil {
logger.Warn("Failed to change to project directory %s: %v", dir, err)
tui.ShowBanner(
"Directory Change Failed",
fmt.Sprintf(
"Could not change to the project directory %s: %v\n\n"+
"Please navigate to the directory manually or use the --dir flag.",
dir,
err,
),
false,
)
os.Exit(1)
}
🤖 Prompt for AI Agents
In internal/project/project.go at line 644, the call to os.Chdir(dir) lacks
error handling, which can cause silent failures if changing the directory fails.
Modify the code to capture the error returned by os.Chdir and handle it
appropriately, such as returning the error or logging it. Also, update the
function's documentation to mention that it changes the working directory,
highlighting this side effect for callers.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants