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.

Sign up for GitHub

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

Jump to bottom

Npe to multisortField when table is not lazy and the multisort is an empty array #14060

Closed
ghost opened this issue Nov 8, 2023 · 2 comments
Closed

Npe to multisortField when table is not lazy and the multisort is an empty array #14060

ghost opened this issue Nov 8, 2023 · 2 comments
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@ghost
Copy link

ghost commented Nov 8, 2023

primeng/src/app/components/table/table.ts

Line 1607 in 97876b9

multisortField(data1: any, data2: any, multiSortMeta: SortMeta[], index: number): any {

When i using the multiSortMeta from p-table with the SortMeta as empty array or undefined and the table is configure as lazy false this error are display:

image
@github-actions github-actions bot added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 8, 2023
@ghost ghost changed the title Npe to multisortField when table is not lazy and the multisort is and empty array Npe to multisortField when table is not lazy and the multisort is an empty array Nov 8, 2023
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

1 similar comment
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mertsincan