-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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.
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
Decimal separator is incorrectly managed by the browsable API #3139
Labels
Milestone
Comments
Now resolved in master - thanks for the report! |
This was referenced Mar 9, 2017
This was referenced Oct 16, 2017
This was referenced Nov 6, 2017
This was referenced Dec 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a model containing FloatField field:
and I have built a browsable API for the model using djangorestframework.
In the put form of the browsable API, the
coste
field is automatically formatted using a comma separator (so3.0
is shown in the form as3,0
). I guess django or djangorestframework are formatting it according to my system locale.However, if the form is submitted an error because of the number formatting:
HTTP 400 Bad Request
I am aware that djangorestframework does not support localized decimal fields (according to #2897), but I would expect that it is able to create a non-localized field which correctly works on a localized environment.
The text was updated successfully, but these errors were encountered: