Debug logging

[mstade]

From @mstade on August 12, 2014 9:41

When you make requests to resources that don't exist in a web, there's currently no information to let you know it was a 404. We should add this, and other things, that make debugging easier.

Copied from original issue: sammyt/nap#17

[mstade]

From @haggyj on August 12, 2014 17:9

@aaronhaines did this via middleware in our sugary syntactic wrapper.

[mstade]

That's pretty sweet dude. Should probably be part of nap though, we should be friendlier. We were also talking today about potentially hooking into the network tab to log requests. Would be nifty.

[mstade]

From @haggyj on August 13, 2014 9:20

👍

[mstade]

From @aaronhaines on August 14, 2014 5:55

We have a couple of default middlewares we use - for logging and for
handling request timeouts.

We could just bundle those with nap.

On Tuesday, August 12, 2014, Marcus Stade [email protected] wrote:

That's pretty sweet dude. Should probably be part of nap though, we should
be friendlier. We were also talking today about potentially hooking into
the network tab to log requests. Would be nifty.

—
Reply to this email directly or view it on GitHub
sammyt/nap#17 (comment).

[mstade]

From @aaronhaines on August 15, 2014 7:5

Actually there is an example in examples/middleware.html

[mstade]

There are some nifty ideas presented in gaearon/redux-devtools, and as @janesconference notes in #14 actions aren't that dissimilar from requests. It'd be interesting to see what we could do in terms of logging request/response flows. Especially interesting if coupled with immutable requests/responses, we could actually look into modifying those logged flows. So for instance, a request is made to view something, but the selector is wrong. Instead of having to reload anything, we could potentially just change that request (possibly using hot reloading of request handlers as well) and have the application update accordingly. Also I read or saw somewhere that the same fella wanted to use an action log like that to generate tests. This is a great idea, and could massively improve how we test resources.

[aaronhaines]

In general it would be good to dedicate some time to building debug tooling. Things like Chrome extensions to inspect and discover available resources, test resources in isolation.
It's something that's been on our todo list internally for a while.