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
Is your feature request related to a problem? Please describe.
When storing a number in the triple store, trailing zeroes in the decimals are truncated (ex: 10.50 becomes 10.5).
While this makes very much sense in general, there are situations where you want to show a very specific number of decimals (specifically when using currencies). Example
Describe the solution you'd like
When displaying a currency, it would be nice to have trailing zeroes added to show cents. Example, 10.5 CHF should show as 10.50.
I would like for visualize to check if the number is a currency and display it in a .2f format
Describe alternatives you've considered
This may look like a minor change, but we truly are not used to see currencies truncated and it really looks strange in visualize. It may stay as it is without impacting functionality or correctness in any way, but it remains a nice visual improvement nevertheless.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When storing a number in the triple store, trailing zeroes in the decimals are truncated (ex: 10.50 becomes 10.5).
While this makes very much sense in general, there are situations where you want to show a very specific number of decimals (specifically when using currencies).
Example
Describe the solution you'd like
When displaying a currency, it would be nice to have trailing zeroes added to show cents. Example, 10.5 CHF should show as 10.50.
I would like for visualize to check if the number is a currency and display it in a .2f format
Describe alternatives you've considered
This may look like a minor change, but we truly are not used to see currencies truncated and it really looks strange in visualize. It may stay as it is without impacting functionality or correctness in any way, but it remains a nice visual improvement nevertheless.
The text was updated successfully, but these errors were encountered: