Why is the response wrapped in a data object?

[frederikschubert]

The wrapping of the GET response in a data object forces the user of this lib to perform the same wrapping in his/her backend. This is sometimes not possible. Would it be possible to deliver the pure response data for a GET request?

[wardbell]

Probably could use some flexibility here. An extension point of some kind. Suggest something ... in a PR preferably

[frederikschubert]

I am traveling right now so i cannot contribute with a PR. But wouldn't it be sufficient to change this? I mean just passing back the copy of whatever the user of the lib provided for that resource.

[wardbell]

Please see the discussion of JSON security and best practices in the http chapter. We will keep this default. I am.open to an extension point that let's you return anything you want.

Or fork it and go your own way. This repo exists to support the documentation. It is not intended for real world app development although if it satisfies, that's great.

[frederikschubert]

Ok, thanks for your quick response. I will think about how an extension point might look like and contribute a PR as soon as I am back home.