microsoft / microsoft/vscode-azureresourcegroups
[CoR] Approval card text is improperly wrapped in default Chat layout
Nobody has claimed this yet.
- 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
VS Code Insiders Version: 1.137.0-insiders
Repro Steps:
- Create a project using Azure Project with a project description: a to-do list web app with a REST API and a database.
- Generate a project plan.
- Wait for an approval request to appear in the chat panel.
- Observe the approval card displayed in the default Chat layout.
Expect:
The approval message should be displayed in a readable format. Text should wrap naturally and remain readable without requiring users to resize the Chat panel.
Actual:
The approval card renders the prompt with excessive word breaking. The approval request becomes difficult to read and understand until the Chat panel is manually widened.
More Info:
- Reproduced during Project Plan generation.
- The issue occurs in the default Chat layout.
- Expanding the Chat panel immediately restores correct rendering.
- Appears to be a layout or text-wrapping issue specific to approval cards rather than the approval content itself.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by generating a project plan and viewing the approval request in the default Chat layout, then compare it with a widened Chat panel. Trace the approval card rendering entry point and verify that its text wraps naturally and remains readable without resizing the panel.
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