mongoose-paginate icon indicating copy to clipboard operation
mongoose-paginate copied to clipboard

ES6 6.0 / Node v4.2.4+ Peer Review for v6.0.0

Open edwardhotchkiss opened this issue 9 years ago • 11 comments

  • mostly ready, needs to return a promise always
  • checking for ES5 legacy code
  • MORE tests
  • 2 space indents on everything
  • Documentation - up to date?

If you guys have a few mins! @Jokero @niftylettuce @tsm91 @MatthewRayfield @connected-dalmer @villesau @shime - also please make sure that you are in contributors in package.json, thanks!

edwardhotchkiss avatar Jan 04 '16 01:01 edwardhotchkiss

@Jokero - made the changes, need to figure out why tests are failing with some debugging later today. Thanks for the review!

edwardhotchkiss avatar Jan 08 '16 18:01 edwardhotchkiss

@Jokero Check it out, all tests passing. Looks pretty sexy. We can make some code smaller but it seems to be working great now. Thoughts on release as v6.0.0?

edwardhotchkiss avatar Jan 09 '16 05:01 edwardhotchkiss

@Jokero I added back paginate.options, the id field is back. One issue left is the limit : 0. The test was passing because of how the query was built. I think that no one will ever use limit as zero. Thoughts? Otherwise I think that we're good to go. :8ball:

edwardhotchkiss avatar Jan 10 '16 19:01 edwardhotchkiss

Also all tests passing except with limit zero.

edwardhotchkiss avatar Jan 10 '16 19:01 edwardhotchkiss

I use limit: 0 because it's useful in rest api to get only metadata (page, total, but not documents). Maybe anyone else uses this functionality

Jokero avatar Jan 10 '16 21:01 Jokero

Yeah limit:0 in MongoDB defaults to all docs as the default behavior. I'll make sure that there is a note of it in the docs.

edwardhotchkiss avatar Jan 11 '16 00:01 edwardhotchkiss

Pagination is fetching and counting. If we set limit: 0 we disable fetching. It's very cool

Jokero avatar Jan 11 '16 12:01 Jokero

@Jokero limit:0 back to original ... :8ball:

edwardhotchkiss avatar Jan 11 '16 17:01 edwardhotchkiss

Is this due to be merged sometime soon?

Reason being is that I want to start adding a feature but I don't want to do it on the old codebase and end up in merge hell :)

antony avatar Jun 27 '16 10:06 antony

@antony see #93 — wanna continue bringing this PR forward?

simison avatar Aug 31 '16 12:08 simison

Ah that's terrible news. Sorry to hear it.

@simison I can have a look at getting this PR finalised, I'm quite time constrained so I don't know how soon I'll be able to do it, but I'll update this ticket as I progress.

antony avatar Aug 31 '16 14:08 antony