Provide a means for implementors to be able to access the final API request made

[apotek]

Description

Code that uses this library can pass parameters to the request and get back response data. However, for diagnostics, a user of this library might need to be able to track the actual request that was made, for debugging, testing, etc.

If the Endpoint class could provide a method to return the actual request made (either as a Request object) or as a simple string consisting of METHOD PATH PARAMS, that would help in being able to track the actual behavior of the API.

Issue Owner

@apotek

Proposed Solution

The Endpoint parent class (and interface) should have a getRequest() method that always contains that most recent request made by the class.

This means that the Endpoint, when making the request, would need to store the Request (or request string) to a class variable (or similar) just before or after making the request.

Alternatives Considered

Additional Context

Tasks

Beta Give feedback

No tasks being tracked yet.

[adamzimmermann]

a user of this library might need to be able to track the actual request that was made, for debugging, testing, etc.

I encountered this very thing multiple times, so I'm in full support of this. It was hard to figure out exactly where in the code you could find the literal HTTP request string with all of the additions/alterations/etc.