Is there a small example to understand the error handling of Kiota?

[全自动盒子 (sixwaaaay)]

Runtime behavior
At runtime, if an error status code is returned by the API, the request adapter will follow this sequence:

If a mapping is present for the specific status code and if the response body can be deserialized to that type, deserialize and throw.
If a mapping is present for the corresponding range (4XX, 5XX) and if the response body can be deserialized to that type, deserialize and throw.
Otherwise throw a new instance of the API exception defined in the abstractions library.
The generated clients throw exceptions/errors when running into failed response codes to allow the consumer to tell the difference between a successful response that didn't return a body (204, etc...) and a failed response. The consumer can choose to implement try/catch behavior that either catches the generic API exception type or is more specific to an exception type mapped to a range or even a status code depending on the scenario.

ref: doc: Runtime behavior

[Vincent Biret (baywet)]

Hi 全自动盒子 (@sixwaaaay)
Thanks for using kiota and for reaching out.
Can you please provide more details about what you're looking for? How should your application handle the exceptions? Something different? In which language? Thanks!

[Kenneth Hoff (KennethHoff)]

You can see some discussion on that topic here, where I (and some other dude) went through a few phases to understand what was going on.