Rename from "top" to "maxCount" in paging operations #9505
Merged
+49
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
microsoft-github-policy-service
bot
added
the
emitter:client:csharp
Contributor
|
No changes needing a change description found. |
JoshLove-msft
approved these changes
Jan 29, 2026
radhgupta
requested review from
christothes,
jorgerangel-msft,
jsquire and
m-nash
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the C# HTTP client generator to improve parameter naming consistency for paging operations. Specifically, it ensures that the "top" query parameter is renamed to "maxCount" in generated REST client methods, and adds a corresponding unit test to verify this behavior. Additionally, the
InputParameter.Updatemethod is enhanced to allow updating multiple fields at once.Solves: #9502