[MPG] Generate diff of generated SDK between swagger and typespec #2312
Open
16 of 18 tasks
Labels
discussion
An area of design currently under discussion and open to team and community feedback.
mgmt
This issue is related to a management-plane library.
MPG generate diff for azure-mgmt-sphere: https://apiview.dev/Assemblies/Review/f48fd53f674c4657a064361ee8dd0859?revisionId=c635cb1ae6ee4ef991528b33ea20042c&diffOnly=False&doc=False&diffRevisionId=880ae55cfe1742649ef8f9ddf4cda63b
Python specific
HttpRequest/HttpResponse
changes from azure.core.pipeline.transport to azure.core.restsend_request
for client (API change)stream
(API change): parameters in docstring but not in method signature #2363maxpagesize
(API change)ArmOperationStatus
of SDK generated from typespec #2584OperationListResult
is renamed toPagedOperation
and not used #2585JSON
for_xxx_initial
operation #2597header
andquery
signatures changes from positional to keyword-only #2612across language
Resource
is renamed toArmResource
(same forProxyResource
andTrackedResource
): resource model changes of generated SDK code based on TSP compared with swagger typespec-azure#104ArmResource
lacks propertyname
. (Maybe fixed by https://github.com/Azure/typespec-azure/pull/736/files#diff-823f10c1812ffa803f58da35c7d41623a79c2e5c37f0c15d09ce66bcfdcfbe97 but need check)SystemData
is marked asreadonly
: [MPG][Diff] properties ofSystemData
is marked asreadonly
#2553model UserAssignedIdentities is Record<UserAssignedIdentity>;
typespec-azure#825 and [Bug]: New modelUserAssignedIdentities
will cause breaking changes for SDK typespec-azure#824issue
The text was updated successfully, but these errors were encountered: