Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove special parameter ordering for contentType #6779

Closed
JoshLove-msft opened this issue Mar 31, 2025 · 0 comments · Fixed by #6780
Closed

Remove special parameter ordering for contentType #6779

JoshLove-msft opened this issue Mar 31, 2025 · 0 comments · Fixed by #6780
Assignees
Labels
emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp

Comments

@JoshLove-msft
Copy link
Contributor

We have special ordering in RestClientProvider for contentType parameter, but this assumes that the contentType is optional. The contentType could be required. I'm not sure if the intent was to make the contentType the first optional parameter, in which case we could consider making it the first required parameter (if required), but there doesn't seem to be a good reason to not just use the spec-defined ordering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant