Hook into the middleware to allow custom response processing

[Addvilz]

Summary

This relates to custom implementations.

It would be great if we could somehow hook into the middleware to be able to modify the response behaviors based on the interruptions and add custom logic on top of that

Currently, there is no way to hook into the middleware and intercept responses while also having access to Interruption

Basic example

Example would be an ability to, based on, for example, rule IDs or other data, to return custom responses to the client.

Motivation

There is a workaround (entirely custom middleware implementation) but this is cumbersome and hard to maintain long term.

[jcchavezs]

Check this thread #774. If you have concrete examples we could think of adding something in the line of #774 (comment) but again without concrete use cases we might not add the abstraction.

[Addvilz]

@jcchavezs For example, I’d like to be able to provide users with helpful errors in certain cases, or for example, allowing a captcha pass to ignore certain rules.

I believe #774 could help with this, but I think adding hooks into WrapHandler would be a better solution - for the reasons you mentioned: avoiding internal leaks and not having to maintain a custom WrapHandler implementation in sync with the original. Simply having access to the Interruption object would be sufficient.

The key for me is ability to accsss the Interruption and the data within. That's all.

[jcchavezs]

thanks for the feedback @Addvilz. I you show me some code consuming this I am open to add this feature. In general we are more open to discuss features when there code that shows the use case and helps to design the API. Still this feels like something people wants to use so I am happy to pursue this.

[Addvilz]

@jcchavezs Not sure what do you mean by some code consuming this - it's not a feature that exists, so there can't be code that uses it... Did you mean an example of how it <> work potentially?