Releases: michaelbromley/angularUtils-pagination
Releases · michaelbromley/angularUtils-pagination
Release 0.8.3
- Fix IE8 error caused by undefined constant, see michaelbromley/angularUtils#184.
- Give warning rather than throw exception when matching directives not found, michaelbromley/angularUtils#175, fixes michaelbromley/angularUtils#169
Release 0.8.2
[chore] update bower & npm version numbers to match release.
Release 0.8.1
Fixes broken bower.json file.
Release 0.8.0
- New optional attribute on the pagination controls directive:
auto-hide
. When set to false, the default template will not hide when pagination is not required. (see michaelbromley/angularUtils#165) - Fix to allow expressions of the type `dir-paginate="item in filtered = (collection | itemsPerPage: 10)" (see michaelbromley/angularUtils#155)
- Add "angular" dependency to bower.json for correct operation with Wiredep et al. (see michaelbromley/angularUtils#167)
- Add CommonJS support (see #4)
- Add packaging support for Meteor.js (see #5)
Release 0.7.0
- The pagination controls template is now embedded within the JavaScript file, so no external HTML template is required by default. External files may still be used if desired with the existing configuration methods.
Release 0.6.1
- Force the pagination control directive setCurrent() method to parse the value as integer. See michaelbromley/angularUtils#140
Release 0.6.0
- Fixes sketchy behaviour when using multi-element mode. A totally new implementation is used which enables true feature-parity with ngRepeat in multi-element mode.
- Major refactoring to improve readability.
Release 0.5.1
- Bugfix for onPageChange callback firing on page load when the controls appear in the template before the pagination (see michaelbromley/angularUtils#112 (comment)).
Release 0.5.0
- The dirPaginationControls directive now exposes a
range
object which can be used in the template to allow things like "displaying x - y of z items". - Enables the use of expressions in the
pagination-id
attribute, which in turn enables the use of multiple independent pagination instances generated by an ng-repeat. - Simplifies the API by not requiring the pagination id to be specified as a second parameter in the
itemsPerPage
filter.
Release 0.4.0
- Add paginationTemplateProvider, which allows the pagination controls template to be specified globally from your app's config block. See the docs for details.
- Add watcher on itemsPerPage to allow correct updating of async data - see michaelbromley/angularUtils#80