Skip to content
Branden Horiuchi edited this page Apr 28, 2016 · 9 revisions
  • 4/28/2016
    • handling case where either an options or request object was not specified to paginate. Previously this would not return any relations or page calculations. Resolved by defaulting to an empty hash.
    • published 1.0.6 to npm
  • 4/22/2016
    • updated dependencies to latest
    • added path option to paginate to override the displayed resource path
    • published 1.0.5 to npm
  • 2/21/2016
    • added a check for the database type in order to identify the correct table/column escape
    • added case insensitive like (ilike) to postgres search to match mysql like functionality
    • published 1.0.4 to npm
  • 1/26/2016
    • removed ` from queries for postgres compatibility
    • published version 1.0.3 to npm
  • 1/19/2016
    • Made request.query the default field to search for query parameters since express uses this field by default
    • Began deprecation of useQuery option since it is now the default
    • Added the queryField option to allow for the query field to be dynamically specified regardless of the server framework being used.
    • Published version 1.0.2
  • 11/7/2015
    • Fixed an issue with filtered page count
    • added transaction support
    • added useQuery option to the paginate function
    • Published version 1.0.1
  • 11/5/2015
    • Created WIKI
    • Re-designed module to work with bookshelf chained methods
    • Re-designed pagination configuration schema
    • Published version 1.0.0