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
Running the weekly open Api refresh pipeline updates the sliced Open Api files in PowerShell with duplicate operation Ids causing AutoREST build failures.
When the refresh runs, there is a ForceRefresh query parameter passed to DevX and my expectation is that no stale data will be downloaded. Is there something else that needs to be done to ensure freshness of data?
The issue causing the duplicate Id is the singularization logic in devX api which we discovered due to updated groupings of paths( paths for functions/actions moved to other files making the bug apparent) due to the issue at #605.
For now we can close this specific issue(regarding duplicate operation ids) as it is not an issue with the library and follow it up on devXApi via microsoftgraph/microsoft-graph-devx-api#2255
I'll also provide more details on the tags grouping issue at #605
Running the weekly open Api refresh pipeline updates the sliced Open Api files in PowerShell with duplicate operation Ids causing AutoREST build failures.
This is an example of a call made to DevX API to slice the larger Open API file to small files based on tags passed to the service.
https://devxapi-func-prod-eastus.azurewebsites.net/$openapi?tags=^users.calendar$&title=Calendar&openapiversion=3&style=Powershell&fileName=powershell_v2&graphVersion=v1.0&singularizeOperationIds=true
If you execute a
GET
request and search foruser.calendar.calendarView.instance_ListExtension
, you will see that the operation Id has been assigned to two different paths.Attached is a file showing all the duplicated operation Ids for v1.0 paths.
duplicateOperationIds.csv
The text was updated successfully, but these errors were encountered: