Returning DTOs from paginated requests

[pindab0ter]

First of all, thanks for this amazing project. I love the way to abstract away API interactions and make them incredibly friendly to use, especially with the DTOs.

Re #191, I've looked into making this work, and I would like your feedback.

The pagination plugin has functions like items() and collect(). My thought was to create DTO versions dtos() and collectDtos(). I had a working prototype up fairly quickly, but ran into the following design problem.

The request class implements a function called createDtoFromResponse that returns any kind of object, whereas the pagination extension deals with 'items' as members of an array under a key in the response. It's this one/many discrepancy that I would like input on.

It makes sense to have the request decide how to transform any individual response into an array of DTOs. I would like createDtoFromResponse to be that place, but I don't think it can be, as it returns a single object.

The next best thing would be to make an interface with a method createDtosFromResponse that returns object[]. I think that creating DTOs out of the data should be the responsibility of the Request class.

I would like your thoughts @Sammyjo20. As we need this for a project, I would like to collaborate to make this a part of the pagination plugin in a way that suits not only our but most people's needs.