[TypeSpec Authoring][Benchmark] Support updating template parameter (advanced ARM case)
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Parent epic: #15725
Add advanced ARM benchmark case(s) covering **updating a template parameter** on an existing TypeSpec ARM resource.
Real-world example:
https://github.com/Azure/azure-rest-api-specs/pull/43317/files#diff-613718fe62eeb5c97a49a24d4d4ec6ba20151f340bfb1d77226668d655a4ec9f
Scope:
- Capture the scenario from the linked PR as a benchmark stimulus (before/after TypeSpec inputs, expected outcome).
- Cover the common variants for changing a template parameter on an Azure.ResourceManager template (e.g., `TrackedResource`): renaming the properties type, swapping/extending properties model, changing constraints, etc.
- Add graders that verify both syntactic correctness (compiles, validates) and semantic correctness (resulting Swagger/OpenAPI matches expectations from the real PR).
- Ensure the case lives alongside the other advanced ARM cases added under #15725.
Contributor guide
Research direction
Start by inspecting the advanced ARM benchmark cases added under parent issue #15725, then study the linked Azure REST API PR for the before-and-after TypeSpec inputs and expected Swagger/OpenAPI result. Define the benchmark stimulus for updating a template parameter and add graders for compilation, validation, and semantic output matching across the listed variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100