Skip to content

optimization - use components for collection responses #125

@baywet

Description

@baywet

Today each OData collection response (Collection(X)), the conversion process is inlining the response schema for each operation (object with value + next link...)
However through Microsoft Graph, we do have a lot of endpoints returning a collection of the same thing:
Collection(Message) is returned by /me/messages, /me/messageFolers/{id}/messages, the same endpoints under /users and /groups....
Inlining those schemas results in a lot of duplication, longer descriptions and duplicated classes for code generators.
The conversion process should be declaring components instead and re-using them through multiple endpoints.

Metadata

Metadata

Assignees

Labels

fixedtype:enhancementEnhancement request targeting an existing experience.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions