Detailed description

This is a feature request. Many external APIs have shallow rate limits. This means if you have an influx of calls to this API it's very likely you'll hit the limit and the call will fail. It would be great to be able to support defining a rate limiting strategy for a connector and provide the ability to retry after so long.

Context

Why is this change important to you? How would you use it?

• It's something I've hit frequently while working with remote APIs, I'd use it for multiple integrations I've built.

How can it benefit other users?

• Avoid hitting rate limits, losing data in failed calls

Possible implementation

N/A

Hey @jenky

I noticed that this library has plagiarised a lot of my documentation from my library, Saloon: https://docs.saloon.dev/

The introduction of your documentation is almost exactly the same as my documentation from a few versions ago

Saloon's Docs:

I also noticed quite a few other pages have been simply copied and not re-written.

I'm flattered that people are writing similar libraries to Saloon, but I'm not cool with people copying the writing that I spent a lot of time on.

Detailed description

Improve decoder decode method to return iterable instead of array

Context

This allows to map the response body to DTOs