Middleware Upgrade: Usage & Discussion about resourcejs HOT 7 CLOSED

OK, so you have thought of everything :-)

I was wandering through the resourcejs code wondering how to block the response.Maybe I would create a flag on on the req, maybe I would call that flag noResponse.

So you can imagine my surprise when I came across this line:

    respond: function(req, res, next) {
      if (req.noResponse || res.headerSent || res.headersSent) { return next(); }

So I updated my example above to:

router.get '/test4/:key', (req, res, next) ->
    req.noResponse = true
    resj = req.app.resourcejs
    async.waterfall [
        (cb)->
            req.query.key = req.params.key
            resj['/api'].get.call this, req, res, ->
                return cb res.resource.status unless res.resource.status is 200
                cb null, res.resource.item[0]
        (api, cb)->
            req.body =
                key : api.key
                vid : '123'
                mac : '123'
            resj['/verification'].post.call this, req, res, ->
                return cb res.resource.status unless res.resource.status is 201
                cb null, res.resource.item
    ], (err, verification)->
        return res.sendStatus err if err?
        res.render 'verify', title:'verify', vid:verification.vid

And everything worked beautifully. Wonderful.

So now the question is: Who is going to update the readme so all this stuff is actually documented?

from resourcejs.

@biofractal hah glad you got things worked out!

If you feel so compelled, you can submit a pr to update the README. Unfortunately I am currently swamped so I cant currently do it myself, but if you dont do it, I'll do it when I catch my breath!

Let me know what you decide.

from resourcejs.

@biofractal I just opened 2 issues to help get the ball moving: #15 and #16

I think these are key components of ResourceJS that are currently undocumented, but allow pretty seamless integration with any codebase. Having these documented throughly could ward against simple issues that arise in the future!

from resourcejs.

I gave both of you access to push to this repo, so whoever does it, the other one can accept the pull request. Thanks for your help.

from resourcejs.

@travist thanks, will do!

from resourcejs.

Added #18 and #17 - I will take those.

from resourcejs.

Do we want to just create one big readme - or should we be splitting this down wiki-style?

from resourcejs.