Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
baywet opened this issue Oct 16, 2024 · 0 comments · Fixed by #597
Closed

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

baywet opened this issue Oct 16, 2024 · 0 comments · Fixed by #597
Labels
priority:p0 Blocking issue/ loss of critical functions. An ICM may be filed to communicate urgency. SLA<=48hrs type:bug A broken experience type:regression A bug from previous release

Comments

@baywet
Copy link
Member

baywet commented Oct 16, 2024

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.

@baywet baywet added priority:p0 Blocking issue/ loss of critical functions. An ICM may be filed to communicate urgency. SLA<=48hrs type:bug A broken experience type:regression A bug from previous release labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:p0 Blocking issue/ loss of critical functions. An ICM may be filed to communicate urgency. SLA<=48hrs type:bug A broken experience type:regression A bug from previous release
Projects
None yet
1 participant