feat(dotnet): use build-client-streamed for .NET SDK

[daniel-jonathan]

Summary

Use build-client-streamed for .NET SDK to include streaming endpoints.

Changes

• Makefile: Switch build-client-dotnet to use build-client-streamed (aligns with Python SDK and JS SDK feat(js): use build-client-streamed for JS SDK #657)

Related

• feat: add StreamedListObjects support openfga/dotnet-sdk#156
• [All SDKs] Support streaming endpoints (StreamedListObjects) #76
• feat(js): use build-client-streamed for JS SDK #657

Summary by CodeRabbit

• Chores
  • Updated the .NET client build process to use an optimized build variant.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A Makefile modification switches the build-client-dotnet target to invoke build-client-streamed instead of build-client, while maintaining identical parameters for the OpenAPI generator invocation.

Changes

Cohort / File(s)	Summary
Makefile target update Makefile	Modified build-client-dotnet target to call build-client-streamed instead of build-client with the same parameters (sdk_language=dotnet, tmpdir, OPENAPI_GENERATOR_CLI_DOCKER_TAG)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify that the build-client-streamed target exists and accepts the same parameters as build-client
• Confirm that switching to the streamed variant is the intended behavior for the .NET client build

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: switching the .NET SDK build process to use the streamed variant for building the client.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[rhamzeh]

Nice! Thanks @daniel-jonathan!

I'm slightly surprised we did not need similar changes on the Python, JS, Go and Java SDK fronts - I would have expected that the streaming endpoint required similar special handling across all SDKs.

cc @SoulPancake

[daniel-jonathan]

Nice! Thanks @daniel-jonathan!

I'm slightly surprised we did not need similar changes on the Python, JS, Go and Java SDK fronts - I would have expected that the streaming endpoint required similar special handling across all SDKs.

cc @SoulPancake

Thank you! I will review the js-sdk in a moment, and then discuss with @SoulPancake about the others.

[SoulPancake]

@rhamzeh @daniel-jonathan so Basically didn't need it in SDK-generator in go/java as I just created a separate file instead of the config/clients/dotnet/template/api.mustache
Just to avoid having to change the generator with the changes required in the API layer.

So essentially, same layer, but the file doesn't come from the templates