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
Currently, the visual validation of input when adding/modifying objects is not the best, especially for numeric types.
The default way antd handles NumberInput components is that it allows visually inputting everything in it. Only after clicking outside of the window, it visually discards changes that aren't assignable to the given type.
It's only after clicking outside of the input field, that it comes back to being 0.
It can be confusing, especially if a floating point number is provided in an integer input field.
After clicking outside the input field goes back to:
The text was updated successfully, but these errors were encountered:
Currently, the visual validation of input when adding/modifying objects is not the best, especially for numeric types.
The default way antd handles NumberInput components is that it allows visually inputting everything in it. Only after clicking outside of the window, it visually discards changes that aren't assignable to the given type.
It's only after clicking outside of the input field, that it comes back to being 0.
It can be confusing, especially if a floating point number is provided in an integer input field.
After clicking outside the input field goes back to:
The text was updated successfully, but these errors were encountered: