Skip to content

Ambiguous call sites in pageable methods between protocol and convenience #7636

Closed
@JoshLove-msft

Description

@JoshLove-msft

I think this is because our logic to determine if we need required parameters in protocol methods looks to see if the parameter types match. If all parameters are optional, then the type matching shouldn't matter, and the protocol method should have at least the first parameter be required.

Metadata

Metadata

Assignees

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