You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DPG generation for @azure/schema-registry package using this tsp file generates a conflict within the same module. See the duplication for the CustomPage interface in the models.ts module below.
For more reference, here is the generated file. We expect the generated file would not have this conflict.
/** Paged collection of Version items */exportinterfaceCustomPage{/** The Version items on this page */value: Version[];/** The link to the next page of items */nextLink?: string;}
/** Paged collection of SchemaGroup items */exportinterfaceCustomPage{/** The SchemaGroup items on this page */value: SchemaGroup[];/** The link to the next page of items */nextLink?: string;}
@minhanh-phan Thanks for reporting this! The duplicated issue should be fixed in our recent pr but not released yet.
In schema-registry we have the paging operation and please notice that the paging support in modular is still in progress. Not sure we have any timeline for this RP?
listSchemaGroups is resourceOperations.ResourceList<SchemaGroup>;
The DPG generation for @azure/schema-registry package using this tsp file generates a conflict within the same module. See the duplication for the
CustomPage
interface in themodels.ts
module below.For more reference, here is the generated file. We expect the generated file would not have this conflict.
To reproduce:
tsp-location.yaml
with these infoThe text was updated successfully, but these errors were encountered: