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: p-multiSelect don´t work when using in reactive forms #14976

Closed
chrissl33 opened this issue Mar 7, 2024 · 2 comments
Closed

Component: p-multiSelect don´t work when using in reactive forms #14976

chrissl33 opened this issue Mar 7, 2024 · 2 comments
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@chrissl33
Copy link

Describe the bug

When applying the formControlName attribute to the p-multiSelect component instead using the ngModel, the component throws an error:
image

It seems it can´t bind it´s options properly anymore.

Everything working fine, when using ngModel.

Environment

Angular 17
PrimeNG 17.7.0

Reproducer

No response

Angular version

17.0.1

PrimeNG version

17.7.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.11.0

Browser(s)

Chrome (122.0.6261.69)

Steps to reproduce the behavior

  1. Implement p-multiSelect inside form tag

  2. Use formControlName on component

  3. Pass options array of object (e.g.: {label: 'Test', value: 'test'})

  4. Go to frontend

  5. MutliSelect already display wrong item, when pre setting a value
    image

  6. Open the Multiselect inside frontend -> Error appears; loading of options is aborted

Expected behavior

MultiSelect display´s selected value correctly and load it´s options, when using inside reactive forms -> using formControlName attribute.

@chrissl33 chrissl33 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 7, 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 Mar 18, 2024
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 Jul 18, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
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 Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

2 participants