Glenn Matthys

Also 404 for passport-local examples: http://www.passportjs.org/packages/passport-local/: For complete, working examples, refer to the multiple [examples ](https://github.com/jaredhanson/passport-local/tree/master/examples) included. https://github.com/jaredhanson/passport-local/tree/master/examples -> 404

This shouldn't be included into this package because its API allows a custom cache handler. A quick implementation of a sized cache could be: ``` function sizedCache(size) { const track...

Please join the discussion on [this wiki page](https://github.com/acarl005/join-monster/wiki/Proposal:-1-on-1-join) where we can lay down how this API should look like.

I don't see any reason why this couldn't be included. But before its implementation, please discuss the API as described here: https://github.com/acarl005/join-monster/wiki/Proposal:-manual-OFFSET-LIMIT-control

I've been thinking about this and technically these are two queries and thus should result in two database queries. When this happens, perhaps we can spawn some kind of "Super...

Are your dependencies up to date?

You can just wrap your join monster call like this: ``` const joinMonster = require('join-monster').default; const myJoinMonster = (obj, args, ctx, info) => joinMonster(info, ctx, sql => ctx.db.raw(sql).then(dbResult =>dbResult), {...

No merging without tests, sorry. I am open to this offset/limit idea though. API wise it looks good too.

``` sqlJoins: [ (followeeTable, relationTable) => `${followeeTable}.id = ${relationTable}.follower_id`, (relationTable, followerTable) => `${relationTable}.followee_id = ${followerTable}.id` ] ``` should be ``` sqlJoins: [ (followeeTable, relationTable) => `${followeeTable}.id = ${relationTable}.followee_id`, (relationTable, followerTable)...

Can you submit a database schema and some code that produces this error?