Skip to content

LastContractView - handle parameter order changes in operations #7973

Closed

Description

@JoshLove01

There is no semantic difference from a spec perspective if operation parameter ordering is changed. However, this would lead to a breaking change in the generated clients. We should use the LastContractView parameter ordering where available for operations (similar to what we already do for model factory methods).

Metadata

Metadata

Labels

emitter:client:csharpIssue for the C# client emitter: @typespec/http-client-csharp

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions