You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a design question ... I find it unnecessarily verbose to require that you add numeric data properties and bind them to the numeric inputs on much of the API surface. In many cases parameters like min, max, etc. are going to be static values and it would be far nicer if you could just state them in the template like so:
<el-input-number min=0>
I get that native DOM variables are always strings but why not just have these numerics coerced to a number from a string and if NAN presents than throw a user-friendly error message?
The text was updated successfully, but these errors were encountered:
Hello, this issue has been closed because it does not conform to our issue requirements. Please submit issues with issue-generator. More info can be found in #3693.
This is a design question ... I find it unnecessarily verbose to require that you add numeric data properties and bind them to the numeric inputs on much of the API surface. In many cases parameters like
min
,max
, etc. are going to be static values and it would be far nicer if you could just state them in the template like so:I get that native DOM variables are always strings but why not just have these numerics coerced to a number from a string and if NAN presents than throw a user-friendly error message?
The text was updated successfully, but these errors were encountered: