Azure / Azure/azure-sdk-for-net
Code Generator change well-known paging method parameter top to maxCount
Open
Nobody has claimed this yet.
CodeGen
Mgmt
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 5.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 397
Description
Custom code is required to revert the unexpected change, as shown the PR
https://github.com/Azure/azure-sdk-for-net/pull/55531. Management plain Generator or it's upstream Generator should fix the issue at the first place.
Contributor guide
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 by reviewing PR #55531 and the generated paging methods affected by the parameter change from top to maxCount. Trace whether the behavior comes from the Management Plane Generator or its upstream generator, then verify that generated output matches the intended parameter name without custom reverting code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100