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

PrimeNG Radio button not working inside reactive form #15666

Closed
MoInMaRvZ opened this issue May 23, 2024 · 1 comment
Closed

PrimeNG Radio button not working inside reactive form #15666

MoInMaRvZ opened this issue May 23, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@MoInMaRvZ
Copy link

Describe the bug

The p-radioButton component is not working properly when used inside a reacive form.
Everytime when I use the radio button component inside reactive form i can select every radiobutton like seen in this screenshot
image

Environment

<form [formGroup]="hereFormGroup">
<div class="flex flex-col">
      <p-radioButton name="myradiobtn" label="btn1"></p-radioButton>
      <p-radioButton name="myradiobtn" label="btn2"></p-radioButton>
      <p-radioButton name="myradiobtn" label="btn3"></p-radioButton>
      <p-radioButton name="myradiobtn" label="btn4"></p-radioButton>
 </div>
</form>

Reproducer

No response

Angular version

16.2.0

PrimeNG version

16.4.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20

Browser(s)

No response

Steps to reproduce the behavior

  1. Create a reactive form in typescript
  2. Implement form in html template
  3. Use radiobuttons as described in environment above

Expected behavior

You should be able to select only one radio button at a time

@MoInMaRvZ MoInMaRvZ added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 23, 2024
@mertsincan
Copy link
Member

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

2 participants