Skip to content

fix(material/paginator): emit events when page index is updated #30890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

andrewseguin
Copy link
Contributor

Rebased version of #26903

Fixes #26890

@andrewseguin andrewseguin requested a review from a team as a code owner April 16, 2025 22:20
@andrewseguin andrewseguin requested review from crisbeto and mmalerba and removed request for a team April 16, 2025 22:20
@andrewseguin
Copy link
Contributor Author

Will close this to find a different way to solve the issue. Agreed it doesn't seem right that an Input should cause an Output. The paginator is not the source of truth, but the data source treats it like one. Instead Ill explore adding an API to the data source for the app to manually force an emit of new data

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(table): Table data does not get updated when paginator pageIndex is modified
2 participants