Add a test for pre / post middleware in search

[jlopezr]

@Abaena please can you put a comment with the pre / post code that you are using.

[Abaena]

// pre middleware

function filterQuery(Model, req, res, next) {
  if(req.user && req.user.role == "admin") {
    return next();
  } else {
    req.body.query["isActive"] = true;
    return next();
  }
}

// post middleware

function filterActive(config, req, res, doc, next){
  if(doc) {
    if (!req.user || !req.user.role || req.user.role != 'admin') {
        if (doc.constructor == Array) {
            var _docs = doc.filter(function (d) {
                return d.isActive == true;
            });
            next(null, config, req, res, _docs);
        } else {
            if (doc.isActive==true) {
                next(null, config, req, res, doc);
            } else {
                next(null, config, req, res, null);
            }
        }
    }else{
        next(null, config, req, res, doc);
    }
  }else{
    next(null, config, req, res, doc);
  }
}

// injector configuration

search: {
    profiles:{
        _default:{
            populate: ["tags","category",authorWithoutPwd],
            pre: [filterQuery],
            // post: [filterActive],
            mongo: {
                projection: {_id:1, title:1, isActive:1, date:1},
                options: {
                    sort: '-date'
                }
            }
        }
    }
},

[GerardSoleCa]

Hi,

What is exactly happening here? I mean, found a bug, have a problem with "routeinjector hooks"?

[jlopezr]

We found two issues. One is that, when post Middleware is used, SearchCount semantic is not respected. Second, also when post middleware is used, the hard limit feature generates bad results. Both issues have been fixed but I want the examples on the test cases. Juan El sáb., 4 mar. 2017 11:44, Gerard <notifications@github.com> escribió: Hi, What is exactly happening here? I mean, found a bug, have a problem with "routeinjector hooks"? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAooyQapD2HVYZZCS3TD0_YRI1eGuMT6ks5riUCDgaJpZM4MSTKO> .