[Feature Request] VNumberInput allow Parsing and Fallback for min and max Values in VNumberInput

[3dyuval]

Problem to solve

The current VNumberInput does not automatically handle non-numeric min and max values, nor does it provide fallback mechanisms for values exceeding JavaScript's safe integer ranges, resulting in possible input errors or unexpected behavior.

Proposed solution

Implement a parsing mechanism to interpret min and max, and automatically resort to Number.MIN_SAFE_INTEGER or Number.MAX_SAFE_INTEGER when inputs are invalid or exceed safe numeric limits, ensuring robust and predictable component behavior.

Playground

[J-Sek]

min and max are already set to *_SAFE_INTEGER as default:

  min: {
    type: Number,
    default: Number.MIN_SAFE_INTEGER,
  },
  max: {
    type: Number,
    default: Number.MAX_SAFE_INTEGER,
  },

By setting them to Infinity and -Infinity you would override these defaults and accept numbers outside of range that framework defined as reasonable boundaries for typical use. But that's not the problem here anyways.

The problem in the Playground

So adding "1" results in the same value. Seems like it is what "SAFE" means - once you exceeded safe range, math does not apply.

Workaround :step='2'

<v-number-input
  class="max-out-of-range1"
  :max="Number.MAX_SAFE_INTEGER + 2"
  :step="2"
  v-model="value2"
/>

<v-number-input
  class="max-out-of-range2"
  :max="Infinity"
  :step="2"
  v-model="value3"
/>