Add Settings Page with Repository and Local Path Management

[kleneway]

Description

Implement a new Settings page in the application to allow users to manage repositories, configure local paths, update account information, and monitor branch build status. This enhancement aims to improve user experience by centralizing configuration options.

Features

1. Add New Repository

• Functionality: Provide a link/button labeled "Add Repository" on the Settings page.
• Action: Redirects the user to the /settings/repositories page where they can add a new repository.

2. Configure Local Path

• Functionality: Add a link/button labeled "Set Local Path" on the Settings page.
• Action: Allows users to input a path to their local version of the app.
• Integration: When a local path is set, clicking the "Save" button in the chat section will open the save dialog with the specified local path prepended, directing the file to the correct folder.

3. Update Account Model

• Fields to Add:
  • local_path (String): Stores the user's local app path.
  • does_current_branch_build (Boolean): Indicates if the current branch builds successfully.
• Migration:
  • Use the older version of ORM as specified in the project documentation.
  • Refer to existing migration files for examples.
  • Note: Do not attempt to update the app's ORM version.

4. Account Settings

• Email Management: Allow users to change their email address.
• GitHub Integration: Provide an option to disconnect their GitHub account.
• View Account Information: Enable users to view their account details and settings.

5. Branch Build Status

• Functionality: Display the build status of the current branch on the Settings page.
• Implementation:
  • During setup, check if the current branch builds successfully.
  • Set does_current_branch_build to true if the build is successful, otherwise set it to false.

Implementation Details

• UI/UX:

  • Design the Settings page with clear sections for Repository Management, Local Path Configuration, Account Settings, and Branch Build Status.
  • Ensure intuitive navigation and usability.

• Backend:

  • Update the Account model with the new fields.
  • Create necessary migrations using the older ORM version.
  • Ensure data integrity and proper handling of new fields.

Steps to Implement

1. Design the Settings Page UI:

   • Create sections for adding repositories, setting local paths, updating account info, and displaying branch build status.

2. Update the Account Model:

   • Add local_path and does_current_branch_build fields.

3. Create Migrations:

   • Use the older ORM version.
   • Reference existing migration files for structure.

4. Implement Repository Addition:

   • Add the "Add Repository" link/button.
   • Set up redirection to /settings/repositories.

5. Implement Local Path Configuration:

   • Add the "Set Local Path" link/button.
   • Handle input and save the path to the Account model.
   • Modify the chat section's save button to use the local path.

6. Add Account Settings Functionality:

   • Enable email changes and GitHub account disconnection.

7. Display Branch Build Status:

   • Implement logic to check branch build status during setup.
   • Display the status on the Settings page.

Expected Outcome

Users will have a comprehensive Settings page that allows them to manage repositories, configure local paths for saving files, update their account information, and monitor the build status of their current branch. The application will handle these settings seamlessly, enhancing overall usability.

Additional Notes

• ORM Version: Ensure that migrations are created using the specified older ORM version to maintain compatibility.
• Reference: Consult existing migration files for examples to follow the project's standards.

---

--skip-build @jacob-ai-bot

[jacob-ai-bot[bot]]

JACoB here...

You mentioned me on this issue and I am busy taking a look at it.

I'll continue to comment on this issue with status as I make progress.

[jacob-ai-bot[bot]]

Unfortunately, I ran into trouble working on this.

Here is some error information:

400 openai error: Invalid prompt: your prompt was flagged as potentially violating our usage policy. Please try again with a different prompt: https://platform.openai.com/docs/guides/reasoning/advice-on-prompting

[jacob-ai-bot[bot]]

JACoB here...

You mentioned me on this issue and I am busy taking a look at it.

I'll continue to comment on this issue with status as I make progress.

[jacob-ai-bot[bot]]

Update

I've completed my work on this issue and have created a pull request: JACoB PR for Issue Add Settings Page with Repository and Local Path Management.

Please review my changes there.