Andrea Peruffo

An alternative would be to add methods to the `RequestAdapter`, something like: ```java WithHeaders resp = adapter.getWithHeader(() -> client.foo.get()); var headers = resp.headers(); var foo = resp.value(); ... ``` thoughts?

Ack, what would be a reasonable design for this? What we have so far: - current implementation: low level / hard to discover / dependent on http client implementation -...

My personal take is that the current implementation is not enough for the reasons listed here: https://github.com/microsoft/kiota/issues/4698#issuecomment-2122816229 Hoisting it in abstractions means only that it will be a little more...

From the brief description, looks a reasonable design, can you share a draft on how it will look like from the user perspective?

In Java there is Dynamic Proxy, but I would refrain to use it if possible. But we can try to iterate here(in C# no problem!): ```csharp myAdapter.ReturnResponses = true; var...

> didn't want to abstract the response I agree as a "general sentiment", but, in practice, there are several real world use-cases that would take advantage of such functionality. The...

I see this option pretty close to [this](https://github.com/microsoft/kiota/issues/4698#issuecomment-2133187998), but, keeping the static methods away from the adapter is going to make it hard to discover/test/etc. In addition, we already assessed...

Sorry for the delay here. Well, your proposal works and is slightly better than the current status, if this is the best we can agree on, I'll take it. How...

@darrelmiller I think we agreed on having your proposal using callbacks here, do you have a link or a write-up?

> "too harsh during validation and blocking generation early on" is not appreciated but customers I do agree with you, but I have received this feedback as well, and can...