When adding a new API description, Kiota should load with no pre-selected endpoints

[maisarissi]

After creating an API Plugin/client for an specific API, one might want to create another API Plugin/client for the same API but with different endpoints.
So every time a user adds a new API description, even if it's the same OpenAPI description that was load before, Kiota should load the API explorer with no selected paths.

Today, after generating an API Plugin/client, if I try to add the same OpenAPI description to create something different, Kiota loads the previous selected paths.

[baywet]

@maisarissi I think this perception is biased by the fact you're running a lot of demonstrations. Arguably the answer to "are people more likely to generate more clients/plugins with fewer endpoints, or more likely to edit existing plugins/clients?" depends on the kind of work you're doing.
In my experience, unless there are different authentication requirements, or unless the user is working with multiple languages in the same project, it's usually more of a matter of adding something they were missing after generating.

[maisarissi]

I agree with you @baywet . It's more likely that one would want to edit/add something they were missing after generating and this will be done by the "edit paths" scenario, when one is editing the workspace file.
However, after generating, if one tries to add the same API using the "Add API description", which is to create a whole new thing, we should load Kiota with no pre-selected endpoints.

[baywet]

Ah I didn't get the fact this was specifically for the "add API description" flow, not just the auto-reload after generating. Thanks for the precision.

[ElinorW]

Closing this as it was been resolved