Component: p-inputNumber [min] property NaN

[danielvieira1]

Describe the bug

When I specify [min]=null in the p-inputNumber component, this happens:

NaN is set instead of null. I can not enter negative values anymore unless I use the arrow keys.

Environment

I am using regular Angular with PrimeNG

Reproducer

No response

Angular version

17.3.5

PrimeNG version

17.15.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.18.2

Browser(s)

Chrome

Steps to reproduce the behavior

<p-inputNumber
mode="currency"
locale="de-DE"
[min]="null"
currency="EUR"
[ngModel]="null"

Now try to add a negative value without using the step buttons or arrow keys

Expected behavior

if null is specified in the "min" property, you should be able to add negative values.

[RogueTea]

In the demo you are able to use negative numbers without defining a min. Could you please try this and see if it works for you?

[danielvieira1]

Yes, if you don't define it, its fine. It happened for me because I wrapped the primeNG component and default value that is parsed into the primeNG component is null.