-
Notifications
You must be signed in to change notification settings - Fork 34
/series/{id}: show the prices in the same way everywhere #473
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
Comments
@cssru WDYT? I like my approach because it looks more clean and less verbose. In the same time I like your solution because it uses standard utils from Thymeleaf. |
I suggest to use two digits after point. |
Hmm.... Why? It's obvious for me :) |
'cause there is not one euro and a half. 'cause there is one euro and 50 cent. |
Ok, I agree with that. But I don't like to see 80.00 RUB instead of 80 RUB. WDYT about this case then? |
Ok. 80.56 and 80.00 looks in one style, but 80.56 and 80 - in different and then uncool :) |
I suggest to ask for some accountant :) |
I've just asked my wife (she is an accountant) that's why I agreed on 80.50 :) But here is a different area -- we're more close to a shop than to a bank. We don't need to be so strict here and it's better to be human-oriented. For example, I believe that the prices in the shops will look like 80 (instead of 80.00) and 80.5 (instead of 80.50). But maybe I'm wrong here. |
Is I remember prices look like 80.00 written on special tickets. Maybe, in your country they look different? |
To be closer to reality we should write "two ground bucks" :) |
After rewriting to JavaScript/React we might use browser's internationalization: https://blog.bitsrc.io/new-intl-apis-in-javascript-c50dc89d2cf3 |
At present the prices from catalogs and in sellers/buyers block use different ways of displaying and hence they look different (1 vs 1.00 and 1.1 vs 1.10):

We should decide on what way of formatting we're using and use it everywhere.
Related to #198
The text was updated successfully, but these errors were encountered: