[Bug] InputQty allows out-of-range manual input (should auto-correct <min / >max)

[lukaskris]

When using the InputQty widget, manual input into the text field allows values beyond minVal and maxVal without immediate correction. Although checkValue() is called on submit or blur, users can still leave the value invalid while typing.

💡 Suggested Fix:

• Add a debounce listener in onChanged to call checkValue() after short delay (e.g. 300ms), so the field auto-corrects on idle input.

✅ Benefits:

• Smoother UX
• Prevents invalid state in form data
• Ensures onQtyChanged always delivers valid value

✅ Tested Fix (sample):

Timer? _debounce;

onChanged: (strVal) {
  ...
  _debounce?.cancel();
  _debounce = Timer(Duration(milliseconds: 300), checkValue);
}

[pmatatias]

Hi @lukaskris , sorry for the late reply.

In the previous version, I did call checkValue inside the onChange handler. However, I recently removed that and instead added a message to notify users when the value is out of range.

By default, when minVal or maxVal are set, the component automatically checks the value. However, users are still able to manually enter a value outside the allowed range.
For example:

InputQty(
  initVal: 0.0,
  minVal: -100.0,
  maxVal: 100.0,
  steps: 0.1,
)

---

This behavior is actually inspired by one of the e-commerce websites. ( Tokopedia)

[pmatatias]

But I'm open to discussing this. I haven't encountered some of the issues you mentioned yet. Could you give me an example of how this could cause an invalid state in the form data? @lukaskris