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

TreeSelect Component: Enabled filters and checbox selection mode #15092

Closed
samirosmanoviccirtuo opened this issue Mar 19, 2024 · 1 comment
Closed
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@samirosmanoviccirtuo
Copy link

Describe the bug

We are using the TreeSelect component with enabled filters and selectionMode set to "checkbox".

<p-treeSelect selectionMode="checkbox" [options]="options" [filter]="true" [propagateSelectionDown]="true" [propagateSelectionUp]="true" > </p-treeSelect>

When filtering nodes, we encounter a situation where, during filtering, a node that initially has 10 child nodes is selected as 'full' due to the fact that only 1 filtered item remains at the end of filtering. After that, when we close and reopen this component, none of the checkboxes are marked. In this case, we also receive incorrect selected values from the component.

Recording.mp4

As you can see in the attached video, in both cases, "Chile" should be selected as the value.

Environment

Chrome,
Windows 10

Reproducer

No response

Angular version

17.1.2

PrimeNG version

17.7.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.16.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@samirosmanoviccirtuo samirosmanoviccirtuo added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 19, 2024
@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 15, 2024
@mehmetcetin01140 mehmetcetin01140 added this to the 17.16.3 milestone May 15, 2024
@cetincakiroglu cetincakiroglu modified the milestones: 17.18.0, 18.Future May 30, 2024
@mehmetcetin01140
Copy link
Contributor

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

@github-project-automation github-project-automation bot moved this to Done in PrimeNG Dec 16, 2024
@mehmetcetin01140 mehmetcetin01140 removed this from the 19.x milestone Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
Status: Done
Development

No branches or pull requests

3 participants