Releases: michaelbromley/angularUtils-pagination
Releases · michaelbromley/angularUtils-pagination
Release 0.3.2
- Fix page controls listing incorrect page range when collection size changes (michaelbromley/angularUtils#73)
- Allow pagination controls to be linked prior to the paginate directive (see michaelbromley/angularUtils#78)
Release 0.3.1
- Fix erroneous inclusion of a jQuery method
.last()
- replaced with equivalent jQLite method.
Release 0.3.0
- Add support for multiElements, ie
dir-pagination-start
anddir-pagination-end
. This allows the paginated element to span multiple elements. For more information see the explanation on the ngRepeat docs : https://docs.angularjs.org/api/ng/directive/ngRepeat
Release 0.2.6
- Remove redundant classes from template.
- Remove unused variable from paginationService
- onPageChange callback no longer fires on page load - only fires on page change
- Name the compile & link functions for better stack traces
Release 0.2.5
- Fix issue michaelbromley/angularUtils#46, total-items pagination not being updated correctly when set to 0.
- Allow space after itemsPerPage and before colon.
Release 0.2.4
- Fixed type in bower.json file
Release 0.2.3
Changelog:
- itemsPerPage filter uses parseInt to prevent errors when the value is a string
- Fix issues michaelbromley/angularUtils#28 and michaelbromley/angularUtils#37 where dir-paginate breaks when placed inside a directive which uses transclusion.
Release 0.2.2
Updated the defaults
Initial release
I have broken this out from the angularUtils repo so that others may more easily manage dependencies on it.