Skip to content

still getting duplicate operation Ids for optional function parameters #594

@baywet

Description

@baywet

Follow up to #580, for graph v1 we're still getting about ~30 duplicate operation Ids

Assemblies affected

2.0.0-preview.3

Steps to reproduce

Convert Microsoft Graph full v1 with hidi and the OpenAPI conversion settings from the weekly generation pipeline.

Expected result

The operation id, or at the very least the hash at the end, should be different because of the optional parameter for usedRange composable function.

Actual result

The following paths

/drives/{drive-id}/items/{driveItem-id}/workbook/worksheets/{workbookWorksheet-id}/usedRange(valuesOnly={valuesOnly})/column(column={column})
/drives/{drive-id}/items/{driveItem-id}/workbook/worksheets/{workbookWorksheet-id}/usedRange()/column(column={column})

Have the same operation Id drives.drive.items.driveItem.workbook.worksheets.workbookWorksheet.usedRange.columnsAfter-43bb

Additional detail

*Optional, details of the root cause if known.

Metadata

Metadata

Assignees

Labels

priority:p1High priority but not blocking. Causes major but not critical loss of functionality SLA <=7daystype:bugA broken experience

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions