NotFoundHandler should write http.StatusNotImplemented if no handler is registered.

[arf-wolt]

Hello team!

Great library. I was wondering if the server should respond with http.StatusNotImplemented rather than http.StatusNotFound.

The reason is that some of the APIs return a 404 as a legitimate response. This should make sure it flags it as a missing handler.

What are your thoughts?

[migueleliasweb]

Thanks!

That's an interesting take. Not sure how to handle this tbh as some other users of this lib could have coded handling the StatusNotFound when testing.

Maybe there could be a way to configure what the behaviour is without breaking compatibility with existing code or possibly create a new function to bootstrap the server that let's you set the response code when a mock is not found?

[arf-wolt]

Thanks for the quick response. I think we could create a new MockBackendOption, something like WithNotFoundStatus, by default, it has http.StatusNotFound, or we can pass in a status?

Though I am sure there is a better way.