Andrea Peruffo

I can have a look but I don't guarantee when 🙂 fortunately just got all the relevant PRs merged and this is not directly on my way at the moment.

Thanks for checking, I confirm I'm not working on this currently (and tomorrow is liberation day in Pt 🙂 ). Happy to see you around picking up the challenges @baywet...

Honestly, I do need to try things out again to assess the current status, I'll try to do it somewhere next week. Feel free to ping me if my delay...

Ok, I took a look at the situation using kiota at version `1.9.0-preview.202311230001`. > any property that "overrides" a parent's type property will get a unique name so it doesn't...

Right, standing an external package's always viable, still I think that it doesn't, easily, enable all of the scenarios. E.g.: it's still going to be tricky to share the native...

Sorry for the delay, I have not forgotten about this, but I wanted to try out a different approach to see how it plays out. The consideration I have made...

Just to state it explicitly, my favorite option would be to have a Kiota Auth layer that can be reused across implementations. I appreciate that the current design doesn't easily...

> authentication providers that are tied to the http client often lack features Correct, I agree, but, at the same time, the current API is limiting the opportunity to write...

Thanks for looping me in @baywet , in my experience, it's rare that ppl will use `jlink` but it is a valid use-case and we want to support it. I...

> I wasn't able to tell how this would be configured in the target projects, especially in the context of generating against multiple APIs in the same project? An example...