CLI generation build failure when an API has paging information but no response body schema

[calebkiage]

The generated code against the latest beta API fails to build for some endpoints because of missing response schemas on pageable endpoints.

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.authenticationEventsFlow
      summary: Get the items of type microsoft.graph.onAttributeCollectionExternalUsersSelfServiceSignUp in the microsoft.graph.onAttributeCollectionHandler collection
      operationId: identity.authenticationEventsFlows.GetOnAttributeCollection.AsOnAttributeCollectionExternalUsersSelfServiceSignUp
      responses:
        2XX: { }
      x-ms-pageable:
        nextLinkName: '@odata.nextLink'
        operationName: listMore
    parameters:
      - name: authenticationEventsFlow-id
        in: path
        description: The unique identifier of authenticationEventsFlow
        required: true
        schema:
          type: string
        x-ms-docs-key-type: authenticationEventsFlow

[baywet]

Thanks for reporting this.
While we could add defensive programming to ignore paging information when no schema is available here, I believe we should also log an issue in the conversion library.
The onAttributeCollection property is a single valued property (not a collection), therefor the paging information should not have been added to the OpenAPI description.
Can you create an issue over there as well please @calebkiage?