Summary of Changes

Hello @fredzqm, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the error reporting mechanism within the VSCode extension for Data Connect GraphQL executions. It introduces a refined data structure to differentiate between HTTP-level response errors and GraphQL-specific errors, ensuring that users receive more precise and actionable feedback when queries fail. The changes also streamline the internal handling of execution results by centralizing error processing and cleaning up unnecessary dependencies.

Highlights

• Refactored Error Handling: Introduced a new ExecutionResults interface to clearly distinguish between HTTP response errors (respErr) and GraphQL errors (gqlErrors) within a successful HTTP response, providing a more structured approach to error reporting.
• Improved Error Display in UI: The Data Connect execution results UI has been updated to explicitly render separate sections for HTTP response errors and GraphQL errors, offering users clearer and more precise feedback on query failures.
• Decoupled Error Processing: The DataConnectService now returns raw HTTP responses, and the logic for processing and structuring these responses, including error interpretation, has been centralized in the execution.ts file.
• Dependency Cleanup: Several unused or transitive dependencies related to browser automation (e.g., puppeteer, chromium-bidi, zod) have been removed from package-lock.json, streamlining the project dependencies.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.