(C) 2014 Martin Wawrusch
Helpers to provide pagination for APIs
So how does this work?
The basic idea is that pagination is a tricky beast, better left to the server. There are a few different approaches to deal with pagination, including adding them to the header. This one is a bit different. We add a _pagination object that contains all the info needed. Here is a typical input and what comes out of it:
result after conversion
See also
- hapi-auth-bearer-mw
- hapi-identity-store
- hapi-mongoose-db-connector
- hapi-routes-authorization-and-session-management
- hapi-routes-status
- hapi-routes-users
- hapi-routes-users-authorizations
- hapi-routes-roles
and additionally
Contributing
- Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
- Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
- Fork the project
- Start a feature/bugfix branch
- Commit and push until you are happy with your contribution
- Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
- Please try not to mess with the package.json, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
Copyright
Copyright (c) 2014 Martin Wawrusch