Generate only the types used by service signatures in C# client proxies - #26205
Merged
Merged
Conversation
maliming
force-pushed
the
maliming/csharp-proxy-types
branch
from
September 29, 2026 10:30
d91343e to
6e6f7ed
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## dev #26205 +/- ##
==========================================
+ Coverage 49.90% 50.30% +0.39%
==========================================
Files 3842 3842
Lines 135458 135739 +281
Branches 10271 10318 +47
==========================================
+ Hits 67597 68279 +682
+ Misses 65823 65407 -416
- Partials 2038 2053 +15 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
EngincanV
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CSharpServiceProxyGeneratornow generates only contract types reachable from service signatures. It uses API assembly metadata and client project assets to avoid regenerating referenced contract types.Nested, generic, and same-named contract types are handled in generated DTOs and proxy signatures.