microsoft / microsoft/vscode-azureresourcegroups

[CoR] Requirements WebView opens before open_requirements_view approval prompt is shown

Open
#1,765 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

AT-CTI CoR
Dominant language
TypeScript
Stars
78
Forks
55
Avg merge
16h 49m
Merged PRs (30d)
139

Description

OS: Win11 x64
Build Version: 0.12.8-alpha.0

Repro Steps:

  1. Open an empty folder.
  2. In Azure Project view, click "Create New Project with Copilot".
  3. Enter a project description: a to-do list web app with a REST API and a database.
  4. Accept downloading agent instructions.
  5. Observe the Project Requirements WebView.
  6. Observe the Copilot Chat tool approval flow.

Expect:
The approval prompt for open_requirements_view should be shown before the Project Requirements WebView is opened.

Actual:
The Project Requirements WebView becomes visible before the open_requirements_view approval card is shown.
Image

More Info:
This issue also reproduces for Azure Deployment Plan Webview.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue from the Azure Project view through Create New Project with Copilot, then trace the open_requirements_view approval flow against when the Project Requirements WebView becomes visible. Done means the approval prompt appears first; also verify the Azure Deployment Plan Webview case.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.