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

Component: Multi-Select #13989

Closed
MatheusGomes01 opened this issue Oct 31, 2023 · 2 comments
Closed

Component: Multi-Select #13989

MatheusGomes01 opened this issue Oct 31, 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

@MatheusGomes01
Copy link

Describe the bug

When I have a multi-select with optionLabel and optionValue and with a custom filter, when I filter by a property other than the optionLabel, it does not return in the view, even though the array has content, and a have delay in show items.

Version 14

Environment

is a simple CRUDS environment

Reproducer

https://stackblitz.com/edit/github-gdp8hq?file=src%2Fapp%2Fapp.module.ts,src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.component.ts

Angular version

14

PrimeNG version

14

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.14.2

Browser(s)

Chrome

Steps to reproduce the behavior

Filter by item with different attributes of optionLabel and OptionValue, but with exitent attribute, and note the delay when exclude or include characters, and note when filter by other attribute, this return of array is not showing in view

Expected behavior

When filter by attribute different optionLabel and optionValue, if contains values in array filtered then show itens

@MatheusGomes01 MatheusGomes01 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 31, 2023
Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in 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
Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in your comment!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

2 participants