Philipp Kursawe

I wanted to emphasise that this rule is important and absolutely doable. I just wanted to start it myself but checked if someone else is already working on it ;)...

Great work so far! I wonder how difficult it would be to transform the sagaMonitor to an actual DevTools monitor.

Some sagas appear as "unknown" in `SagaMonitor`. Anything I can do about that?

yes this looks very dry and also much more RESTful. I'd like the named route to be appended rather than prefixed with the given id. get :edit, :id do #/customer/:id/edit...

get :edit, :id # => "/:id/edit" feels more RESTlike. You specify the resource you want to edit first. Specifiying /edit/ first is RPC style, imho and always bothers me in...

Fully agree with you. Routes should be simple to define in the first place in a REST based app.

Correct, edit is a special representation of the resource. One could argue that not only browsers but other apps could use this representation as well. Say for instance a fat...

I have to agree with @cyb70289 here. A lib should **never** trust user input. It should validate everything and all the time. If "a" isn't a valid base64 string to...

Thinking about it, why is it even relevant in which format the clients sends the data? If this middleware can decode it and provide it as structured data in the...

:+1: Which commit brought that feature into your fork?