microsoft / microsoft/vscode-azureresourcegroups
[CoR] Category creation fails silently when description is shorter than expected
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 Version: Version: 1.137.0
Repro Steps:
- Create a CoR project using the following prompt:
Build an inventory management web app with Microsoft Entra authentication, a REST API, PostgreSQL database, item search, categories, and Azure deployment. - Select "Keep iterating-start debugging and improve my code" and F5 with "Debug All Services".
- Open the "Categories" page and click "Create first category".
- Enter:
Name: test
Description: test
- Click "Create Category".
Expect:
The form should either:
Create the category successfully if the input satisfies backend requirements, or
Display a clear validation message and prevent submission until the input is valid.
Actual:
The button is enabled and can be clicked, but no category is created. No clear validation message explains why the submission failed.
More Info:
- A category could not be created when using a short description such as test, even though the Create Category button was enabled.
- Clicking Create Category produced no visible error message and appeared to do nothing.
- After adjusting the validation logic, the same input successfully created a category, which is now displayed in the Categories list.
- The issue appears to be caused by a hidden frontend validation rule that was not surfaced to the user, resulting in a silent failure.
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
Start at the Categories page's create form and trace the frontend validation and submission path, reproducing the issue with Name and Description set to test. Done means short descriptions either create a category when valid or block submission with a visible validation message; verify the result in the Categories list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100