Description

The maxpagesize parameter from Azure.Core TypeSpec models needs camelCase formatting (maxPageSize) in generated C# code to follow naming conventions.

Implementation Status: Work in Progress

This PR adds the infrastructure for parameter renaming but the visitor implementation is not yet functional. The generated code still produces _maxpagesize instead of _maxPageSize for field names.

Changes Made

• Added MaxPageSizeParameterVisitor: Visitor that detects maxpagesize parameters and attempts to create new InputMethodParameter and InputQueryParameter objects with Name="maxPageSize" while preserving SerializedName="maxpagesize" for wire format
• Updated test expectations: Modified test data files to expect maxPageSize in generated collection result definitions
• Integrated visitor: Added to AzureClientGenerator visitor pipeline early in execution order

Known Issue

The InputServiceMethod.Update(parameters:) call does not propagate parameter name changes to generated code. Field names in CollectionResultDefinition continue using the original parameter name.

Possible causes under investigation:

• Parameter updates may not be persisted through the provider creation pipeline
• Field name derivation may occur before visitor execution or from a cached source
• Different API or pattern may be required for parameter renaming vs. removal

This checklist is used to make sure that common guidelines for a pull request are followed.

• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

• Fixes maxpagesize parameter casing should be camel case #54468

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.