Added typed file-edit models across SDKs - #450
Draft
Aydin Emre Iskender (iskae) wants to merge 1 commit into
Draft
Aydin Emre Iskender (iskae) wants to merge 1 commit into
Aydin Emre Iskender (iskae) wants to merge 1 commit into
Conversation
Author
|
@microsoft-github-policy-service agree company="GitHub" |
|
Aydin Emre Iskender (@iskae) the command you issued was incorrect. Please try again. Examples are: and |
Author
|
@microsoft-github-policy-service agree company=GitHub |
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
1 participant
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.
Replaced raw JSON file-edit fields with shared
FileEditSide,FileEditDiffStats, andFileEditCollectionmodels across the generated SDKs. The models reuseContentRefand preserve JSON field names, nesting, and optionality.Updated the canonical agent guidance to prefer typed models for fixed protocol shapes. Added migration documentation and cross-client coverage.
Compatibility: This breaks affected SDK APIs, including Kotlin source and binary compatibility. It needs breaking SDK releases. Protocol versions stay unchanged.