Distinguish between SSH and DB connection errors

[sweep-nightly[bot]]

Description

This pull request adds functionality to distinguish between SSH and database connection errors in the ConnectionInterface component.

Summary

• Modified apps/studio/src/components/ConnectionInterface.vue
  • Added async testConnection() method to handle testing the connection and displaying appropriate error messages
  • Added async save() method to handle saving the connection information and displaying success/error messages
  • Added handleErrorMessage() method to handle parsing connection URL error messages
  • Modified handleConnect() method to handle connecting to the server and displaying SSH or database connection errors

Fixes #1.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the rope library to refactor Python! Check out Large Language Models are Bad at Refactoring Code. To have Sweep refactor your code, try sweep: Refactor <your_file>.py!
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-nightly[bot]]

Sandbox Executions

[sweep-nightly[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All new business logic should have corresponding unit tests.
• [ ] Apply: Refactor large functions to be more modular.
• [ ] Apply: Add docstrings to all functions and file headers.

[wwzeng1]

fix the linter error here

[sweep-nightly[bot]]

fix the linter error here

Hi @wwzeng1,

I am making the following changes:

File Path

Proposed Changes

apps/studio/src/components/ConnectionInterface.vue

Modify apps/studio/src/components/ConnectionInterface.vue with contents: • Review the changes made in the ConnectionInterface.vue file, specifically looking for common linter issues such as unused variables, incorrect indentation, missing semicolons, or trailing spaces. • If an unused variable is found (e.g., const server which is declared but not used), remove the declaration to resolve the linter error. • Ensure that all new methods (testConnection, save, handleErrorMessage) and the modified handleConnect method adhere to the project's coding standards, which may include proper indentation, use of single or double quotes, and correct placement of braces. • After making the necessary changes to fix the linter error, run the linter locally to confirm that there are no more linter issues with the file.