Prompt to add extension to workspace recommendations when Dev Proxy config detected

[Copilot]

Implementation Plan: Workspace Recommendations Feature

• 1. Add new constants for extension recommendations

  • Add extension ID constant
  • Add file path constant for extensions.json

• 2. Create utility functions for workspace recommendations

  • Function to check if workspace contains devproxyrc files
  • Function to check if .vscode/extensions.json exists
  • Function to check if extension is in recommendations
  • Function to add extension to recommendations
  • Function to prompt user for workspace recommendation

• 3. Integrate recommendation prompt in extension activation

  • Add check during extension activation
  • Show user-friendly prompt if extension not in recommendations
  • Handle user response to add extension to recommendations

• 4. Add tests for workspace recommendations

  • Test detection of devproxyrc files
  • Test checking extensions.json existence
  • Test checking if extension is in recommendations
  • Test adding extension to recommendations

• 5. Address code review feedback

  • Fix storage key handling to avoid special characters issues

• 6. Fix Windows test failures

  • Fixed getFixturePath() to use __dirname instead of process.cwd()
  • This resolves 16 test failures on Windows where fixture files couldn't be found

Summary

Successfully fixed Windows test failures by updating the getFixturePath() function in src/test/helpers.ts. The issue was that process.cwd() returns the VS Code binary directory on Windows during test execution, not the workspace root. Changed to use __dirname which correctly resolves to out/test/ and navigates to the fixture files at src/test/examples/.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Prompt to recommend Dev Proxy Toolkit extension in .vscode/extensions.json when devproxyrc.json or devproxyrc.jsonc is detected</issue_title>
<issue_description>## Problem
When a devproxyrc.json or devproxyrc.jsonc file is detected in the current workspace, the toolkit should help projects recommend the Dev Proxy Toolkit extension for contributors.

Proposed Enhancement

• When detecting a devproxyrc.json or devproxyrc.jsonc in the workspace:
  1. Check if .vscode/extensions.json exists.
  2. If it exists, check if garrytrinder.dev-proxy-toolkit is included in the recommendations array.
  3. If the extension is not present in the array, or if the file does not exist, prompt the user asking if they want to add garrytrinder.dev-proxy-toolkit to the project's extension recommendations.

Benefits

• Ensures contributors are aware of and prompted to install the Dev Proxy Toolkit extension when working on relevant projects.
• Improves onboarding and reduces setup friction for new contributors.

Acceptance Criteria

• On detection of devproxyrc.json or devproxyrc.jsonc, checks for .vscode/extensions.json and presence of the extension in recommendations.
• If missing, prompts the user to optionally add the extension to recommendations.
• Minimal disruption to the user experience (no intrusive popups).
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Prompt to recommend Dev Proxy Toolkit extension in .vscode/extensions.json when devproxyrc.json or devproxyrc.jsonc is detected #303

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[garrytrinder]

@copilot can you take a look at the failed test

[Copilot]

@copilot can you take a look at the failed test

Fixed in commit 8e4b5ec. The issue was in getFixturePath() using process.cwd() which returns the VS Code binary directory on Windows during test execution. Changed to use __dirname which correctly resolves relative to the compiled test files in out/test/.