Skip to content
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

Upon using DataTable Directive in Angular, shows all data on first page itself (no pagination),on deleting any row it still persist on frontend upon page switch #208

Open
Harshad-Lukare opened this issue Jun 3, 2022 · 1 comment

Comments

@Harshad-Lukare
Copy link

Hi Team,

Datatable pagination not working upon performing any activity

1) ISSUE -1

I am Using DataTable Directive in angular (version 13), So in this I fetch data from the pubic api "https://api.covidtracking.com/v1/us/daily.json" and all data shows properly with DataTable pagination

But after refreshing page, it shows all data in first page itself (IT SHOULD SHOW ALL DATA WITH PAGINATION)

All Data shown with Pagination:

DataTable with pagination

After refresh Data shown by DataTable on one Page only:

Datatable not pagination-1

datatable not pagination-2

2) ISSUE 2:

When we click on delete button, selected row gets filter from data array, row gets deleted from frontend also. But upon page switch and come back to page, deleted row still persist in frontend view.

delete row in DT-1

After switch to another page and then back to previous page

DT row deletion-2

BELOW IS MY CODE:

File 1:html file

file1

File 2: .ts file
file2

file2 Continued

file2 continued 3

Please check why DataTable shows this behavior upon deleting any row. Suggest some api by using which we solve pagination
issue in angular(v-13)

@AllanJard
Copy link
Contributor

Thanks for your question. However, per the "New issue" template text and the Contributing document, please post support requests in the DataTables forums. Please also ensure that you link to a running test case showing the issue so it can be debugged. I'm sorry if the new issue text and contributing document wasn't clear enough on that topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants