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 current OpenAPI file for the beta MSGraph endpoint results in descriptions with empty response information for some endpoints. An example is shown below.
Assemblies affected
Which assemblies and versions are known to be affected?1.0.9.0
Expected result
For endpoints that have paging information (x-ms-pageable), the response shape should be known for kiota to generate paging code. @baywet also says that this endpoint isn't actually pageable. See microsoft/kiota#4207 (comment)
Actual result
Failing snippet
openapi: 3.0.1# ...paths:
'/identity/authenticationEventsFlows/{authenticationEventsFlow-id}/graph.externalUsersSelfServiceSignUpEventsFlow/onAttributeCollection/graph.onAttributeCollectionExternalUsersSelfServiceSignUp':
description: Casts the previous resource to onAttributeCollectionExternalUsersSelfServiceSignUp.get:
tags:
- identity.authenticationEventsFlowsummary: Get the items of type microsoft.graph.onAttributeCollectionExternalUsersSelfServiceSignUp in the microsoft.graph.onAttributeCollectionHandler collectionoperationId: identity.authenticationEventsFlows.GetOnAttributeCollection.AsOnAttributeCollectionExternalUsersSelfServiceSignUpresponses:
2XX: { }x-ms-pageable:
nextLinkName: '@odata.nextLink'operationName: listMoreparameters:
- name: authenticationEventsFlow-idin: pathdescription: The unique identifier of authenticationEventsFlowrequired: trueschema:
type: stringx-ms-docs-key-type: authenticationEventsFlow
Additional detail
The text was updated successfully, but these errors were encountered:
The current OpenAPI file for the beta MSGraph endpoint results in descriptions with empty response information for some endpoints. An example is shown below.
Assemblies affected
Which assemblies and versions are known to be affected?
1.0.9.0
Expected result
For endpoints that have paging information (
x-ms-pageable
), the response shape should be known for kiota to generate paging code. @baywet also says that this endpoint isn't actually pageable. See microsoft/kiota#4207 (comment)Actual result
Failing snippet
Additional detail
The text was updated successfully, but these errors were encountered: