Missed this for the headless import

[potofpie]

• need to write env
• api-key flag was wrong

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling during project import, including better handling of cancelled operations and saving projects to disk after import.
• Chores
  • Updated the command-line flag for API key from "apikey" to "api-key".

[coderabbitai]

Walkthrough

The pull request updates the projectImportCmd command by renaming the API key flag from "apikey" to "api-key", adjusts the corresponding code to use the new flag, and removes the old flag declaration and its hidden marking. The import process now explicitly saves the imported project and updates environment variables, with improved error handling for import and save operations.

Changes

File(s)	Change Summary
cmd/project.go	Renamed the API key flag from "apikey" to "api-key", updated flag usage, removed old flag declaration and hidden marking, captured import result, added explicit project saving and environment variable update after import, and improved error handling.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant Importer
    participant Project
    participant EnvManager

    User->>CLI: Run projectImportCmd with --api-key
    CLI->>Importer: Import project using API key
    Importer-->>CLI: Return import result or error
    alt Import successful
        CLI->>Project: Save imported project to disk
        Project-->>CLI: Save result or error
        CLI->>EnvManager: Update environment variables with import keys
        EnvManager-->>CLI: Env update result
    else Import failed
        CLI->>User: Show error and exit
    end

Loading

Possibly related PRs

• Headless import baby #318: Modifies the same projectImportCmd command and API key flag, but in a conflicting manner by adding a hidden "apikey" flag and using it for headless import.

Suggested reviewers

• pec1985
• jhaynie
• robindiddams

Poem

A flag once named "apikey" is gone,
Now "api-key" will carry on.
Projects import, then safely save,
With envs updated, bold and brave.
Errors handled with extra care—
This code hops forward, light as air!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 73fe98b and 4294698.

📒 Files selected for processing (1)

• cmd/project.go (2 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

cmd/project.go (4)

internal/project/project.go (1)

• Project (145-154)

internal/errsystem/errsystem.go (2)

• New (33-63)
• WithContextMessage (100-104)

internal/errsystem/errorcodes.go (2)

• ErrImportingProject (89-92)
• ErrSaveProject (29-32)

internal/apikey/apikey.go (1)

• APIKey (28-40)

🔇 Additional comments (5)

cmd/project.go (5)

804-804: Flag name updated correctly

The flag name has been properly updated from "apikey" to "api-key", which follows kebab-case convention and is more consistent with standard CLI flag naming practices.

---

815-822: Improved error handling and capture of import result

These changes properly capture the import result for later use and enhance error handling with context cancellation detection. This is a robust improvement that ensures clean termination when the user interrupts the operation.

---

823-826: Added explicit project saving after import

The code now properly saves the project to disk after import, with appropriate error handling using the correct error code. This addresses the mentioned issue of needing to write the environment.

---

827-827: Environment variables now saved after import

This change ensures environment variables are properly updated with the API key and project key from the import result, fulfilling the requirement to write the environment.

---

882-883: Removal of old flag confirmed

The code correctly removed the old "apikey" flag declaration and its hidden marking. This avoids confusion and maintains a clean command interface with only the new "api-key" flag.

✨ 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.