Skip to content

remaining duplicate operation Ids for navigation properties on composable functions #596

Closed
@baywet

Description

@baywet

follow up of #594 and #580

Assemblies affected

2.0.0-preview.5

Steps to reproduce

Generate a description for the full V1 of Microsoft Graph with the conversion settings used by weekly generation.

Expected result

Operation Ids to be different.

Actual result

Operation Ids are identical which is invalid.

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

both get

drives.items.workbook.worksheets.usedRange.GetWorksheet

This is caused by the navigation property on the composable function result and the presence of an optional parameter on the composable function.

Other examples

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

drives.items.workbook.worksheets.usedRange.UpdateSort

Additional detail

*Optional, details of the root cause if known.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:p0Blocking issue/ loss of critical functions. An ICM may be filed to communicate urgency. SLA<=48hrstype:bugA broken experiencetype:regressionA bug from previous release

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions