Provide a reference to InMemoryBackendService on function overrides about in-memory-web-api HOT 3 CLOSED

My immediate reaction is that we're overthinking it. If you need to take over an HTTP method, then you take it over. I made some parsing methods available but to turn around and delegate back to the default behavior? Why? OK, I can imagine some use cases but none of them are compelling enough (yet) for me to add this feature.

And if you really want to do that, you can sub-class the InMemoryBackendService itself and take it from there.

Closing for now,

from in-memory-web-api.

I very well could be overthinking it...

There are two situations I could see:

1. My immediate reason I require this is to do authentication. The POST data consists of a user/password and should return a User object.

2. Some endpoints require streams of file data. GET /document/1&type=pdf.

It seems reasonable to be able to call back to the InMemoryBackendService to allow it to handle the request. Am I overthinking this?

from in-memory-web-api.

for the authentication case it's probably possible to create 'auth' collection and provide the responseInterceptor implementation...

from in-memory-web-api.