Closed mikesealey closed 54 minutes ago
Do you reckon there's ever a downside to this? Or could we just bake it in as the default functionality always?
Just going to ship this as the default going forwards because I've often found myself wanting the same thing!
Do you reckon there's ever a downside to this?
Would someone ever use a number column to store binary?
Also some European countries use a full-stop where I would use a comma, and a comma as the decimal point.
Do you reckon there's ever a downside to this?
Would someone ever use a number column to store binary?
Also some European countries use a full-stop where I would use a comma, and a comma as the decimal point.
Locale string is exactly for this :) it will use the correct delimiter according to whatever the user's locale says - so it will be decimal points instead of commas for Europeans for example.
Describe the feature request Create an option in the table to process number columns with commas to separate thousands.
This would likely make use of
number.toLocaleString()
but it would need to impact the display only, and not actually change the value fromnumber
tostring
Currently, the workaround involves a quick formula column, but that approach isn't ideal.
Screenshots