fix(pagination): multiple triggering of pageChanged event #149
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
valorkin
force-pushed
the
fix-page-changed-event
branch
from
9481e5d
to
91c4ec4
Compare
valorkin
added a commit
that referenced
this pull request
Feb 6, 2016
fix(pagination): multiple triggering of pageChanged event
|
We are still seeing this issue in 1.0.23. Has this fix been released yet? Thanks! |
|
Released a long time ago, can you provide plunkr so I can reproduce? |
|
OK, looks like it is an issue with having multiple copies of the same pager in the same template. This may be working as designed and I would like to know how to only fire a single pageChanged event when all of the pagers are using the same ngModel. Any advice? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #76, fix #138, closes #146