As a developer, I want to have a sliced OpenAPI document with only the endpoints and components used by my solution when generating a client about kiota HOT 7 OPEN

I'll jump in on this one. I don't think the goal is to get an OpenAPI document with only the right endpoints. I think the goal is to reuse a similar logic to the one built for plugins instead of having 2 different logic that do very similar things, without being reused. I agree with @baywet, we should absolutely not replace the OpenAPI we cache with a sliced version of it or we'll lose the possibility to expand its capabilities.

from kiota.

Is this for the kiota folder? We should always keep the original description in case the user wants to change their selection IMHO

from kiota.

@baywet This is still unclear. This issue was created to split out #4672 to only work for plugins generation as the questions on functionality in client generation is cleared up.

from kiota.

@maisarissi to provide additional input

from kiota.

That's was exactly my intention, not replacing the copy of the OpenAPI document, but since client generation does "go through" a similar logic as the slicing logic we have for plugins, why not reuse it for client generation, having the slicing logic and then generating the client based on that? Instead of generating all models and then deleting the ones that are not referenced?

from kiota.

where would you place this new sliced description? for plugins it makes sense since it's required by the "engine". For clients we could place it next to the Client class. Thoughts?

from kiota.

In the output folder as an openapi.yaml file would be optimal. That way it live with the code.

from kiota.