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

MultiSelect : Display Limit issue after upgrade #14577

Closed
pjlasl opened this issue Jan 17, 2024 · 3 comments
Closed

MultiSelect : Display Limit issue after upgrade #14577

pjlasl opened this issue Jan 17, 2024 · 3 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@pjlasl
Copy link

pjlasl commented Jan 17, 2024

Describe the bug

We recently upgraded from v15 to v16 and noticed that the multiselect is now capping items to 3 even though you select more.
We have not upgraded our PROD environment to v16 and the multiselect component is working as expected.

We are not using the "selectionLimit" property so it shouldn't limit the display.

The dropdown shows all of the selected options, but the chips cap at 3.

Environment

This is what our multiselect code looks like...we made not changes moving from v15 to v16
<p-multiSelect
*ngSwitchDefault
[ngStyle]="{flex:1}"
[options]="(branches | async)?? []"
[(ngModel)]="criteria.branchList"
defaultLabel="Select Branches..."
display="chip"
appendTo="body"
filterMatchMode="startsWith"
optionLabel="branch"
[disabled]="(branches | async)?.length === 1"
>

Reproducer

No response

Angular version

16

PrimeNG version

16

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.5.0

Browser(s)

Google Chrome

Steps to reproduce the behavior

No response

Expected behavior

No response

@pjlasl pjlasl added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 17, 2024
@HeavyRainLQ
Copy link
Contributor

Input property "maxSelectedLabels" is setted by default to 3. Try to set it to undefined or null if you don't want limit.
However this default value is missing in the doc and should be added. Now the doc is saying is set to null.
Hope it can help!

@pjlasl
Copy link
Author

pjlasl commented Feb 4, 2024

Perfect! I'll try it out.

@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,

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

3 participants