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
I'm use superset container apache/superset where all resources are prepared and I want to change / add another d3-formats for numeric values like currencies Euro / Pound - currently I see only option $,.2f and I'm not able to edit it
How to reproduce the bug
Go to 'Charts'
Go to 'Customize' section and select in 'CUSTOMIZE COLUMNS' the numeric field and click an arrow
popup for changing format will show
Expected results
to change interactively D3 format
Actual results
I can only select from existing list of options
Screenshots
Environment
Containerized solution apache/superset:2.1.0
The text was updated successfully, but these errors were encountered:
In D3 formatter syntax, the $ is just a placeholder for the currency symbol. You cannot just drop in another currency symbol for this. Instead you would do it with a D3 "locale" which is different from a formatter. You can set this for your entire superset instance in config.py if you're close to master (it has not been released in an official Apache version yet).
Given all that, just know that you're not alone... a lot of people are asking for this, and various folks are trying to find the best way forward with an implementation (cc @yousoph@mistercrunch)
For now, this all adds up to more of a feature request than a bug. I'll close this since there's already a discussion open.
I'm use superset container apache/superset where all resources are prepared and I want to change / add another d3-formats for numeric values like currencies Euro / Pound - currently I see only option $,.2f and I'm not able to edit it
How to reproduce the bug
Expected results
to change interactively D3 format
Actual results
I can only select from existing list of options
Screenshots
Environment
Containerized solution apache/superset:2.1.0
The text was updated successfully, but these errors were encountered: