Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

InputNumber decimal bug #5012

Closed
erdun opened this issue Feb 23, 2017 · 6 comments
Closed

InputNumber decimal bug #5012

erdun opened this issue Feb 23, 2017 · 6 comments
Assignees
@afc163

Comments

@erdun
Copy link

erdun commented Feb 23, 2017 •
edited
Loading

when InputNumber is wrapped by getFieldDecorator in Form, it's strange that if input 1.0, it will be 1 when i want to input a number 1.05. It was failed even add the property of 'step'. here's the demo
@lucky3mvp
Copy link

inputnumber 本来就是输入数字的啊，integer啊

@benjycui
Copy link
Contributor

Did you try InputNumber[step]?

It will be better to write your issue/comment in English, so more people can understand you. And this means that more people can help you or benefit from your issue/comment. See: #4897

@benjycui
Copy link
Contributor

And if you still meet this issue, please provide a re-producible demo: http://codepen.io/benjycui/pen/KgPZrE?editors=001

@benjycui benjycui assigned benjycui and afc163 and unassigned benjycui Feb 23, 2017
@benjycui
Copy link
Contributor

It is a problem in rc-input-number's controlled mode.

@erdun erdun changed the title 用this.props.form.getFieldDecorator包裹InputNumberBug InputNumber decimal bug Feb 23, 2017
@erdun
Copy link
Author

erdun commented Feb 23, 2017

thx😊 @benjycui, have rewritten the dec and added the live demo, may help others

afc163 added a commit that referenced this issue Feb 23, 2017
@afc163
upgrade rc-input-number for #5012
f53d0b7
@dispalt dispalt mentioned this issue Feb 23, 2017
Closed
@afc163 afc163 mentioned this issue May 10, 2017
Closed
@lock
Copy link

lock bot commented May 2, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators May 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@afc163 afc163

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@afc163 @benjycui @lucky3mvp @erdun