NumericInput clamps outside bounds with invalid input

[rafeememon]

Bug report

• Package version(s): core@1.35.0
• Browser and OS versions: Chrome 63, OSX Sierra

Steps to reproduce

1.

<NumericInput
  min={1}
  value={this.state.value}
  className="numeric-input"
  onValueChange={this.handleChange}
  clampValueOnBlur={true}
/>

2. Enter "5----" into the input
3. Blur

Actual behavior

handleChange is called with 0

Expected behavior

handleChange is not called. I think I also expect the text to reset to the value prop.

[cmslewis]

@rafeememon FWIW this behavior is intended; it's copied from Sketch's numeric input. Open to changing it if it's unintuitive. @llorca what do you think?

[rafeememon]

Cool, I think it's unintuitive to me because I would expect for any value given to onValueChange to be within the min/max I specify so that I don't need to write my own bounds-checking logic.

[llorca]

@cmslewis seems like reasonable request! why it handleChange called with 0? intuitively I'd guess it wouldn't be called, or be called with null

[giladgray]

given the current behavior, i think handleChange should have been called with 1: the minimum.