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

InputNumber | cannot set value when using reactiveForms #12765

Closed
cetincakiroglu opened this issue Mar 16, 2023 · 1 comment
Closed

InputNumber | cannot set value when using reactiveForms #12765

cetincakiroglu opened this issue Mar 16, 2023 · 1 comment
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@cetincakiroglu
Copy link
Contributor

  • bug: value can be set but the component keeps updating the value
  • expected behavior: Value shouldn't be updated.

Reproducer.

@cetincakiroglu cetincakiroglu added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Mar 16, 2023
@cetincakiroglu cetincakiroglu added this to the 15.Future milestone Mar 16, 2023
@cetincakiroglu cetincakiroglu self-assigned this Mar 16, 2023
@github-actions github-actions bot 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 16, 2023
@cetincakiroglu cetincakiroglu modified the milestones: 15.Future, 15.2.1 Mar 16, 2023
@cetincakiroglu cetincakiroglu removed the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 16, 2023
@cetincakiroglu cetincakiroglu modified the milestones: 15.2.1, 15.Future Mar 22, 2023
@cetincakiroglu cetincakiroglu modified the milestones: 15.Future, 15.4.1 Apr 19, 2023
@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
None yet
Development

No branches or pull requests

2 participants