floating value should be limited to 2 decimal points

[ronakmshah]

This disrupts the view. If showing floating values anywhere, it should always be shown with 2 decimal points max.

[curran]

Related to

• set timestamp to yy:mm:dd:mm:ss in chord table set timestamp to yy:mm:dd:mm:ss in chord table #172 and
• Add configuration option for tick format Add configuration option for tick format #134

[curran]

Related to set timestamp to yy:mm:dd:mm:ss in chord table #172

We can handle this by adding a configuration option for custom formatters for each column of the table. The formatter may be either a number format (hooking into d3-format) or a date format (hooking into d3-time-format).

Here's a sketch of what the configuration might look like:

"data": {
    "columns": [
        { "column": "SrcUplink", "label": "Source Uplink" },
        { "column": "DstUplink", "label": "Destination Uplink" },
        { "column": "PerfMonitor", "label": "Perf Monitor" },
        { "column": "AvgJitter", "label": "Avg Jitter", "format": ",.2f" },
        { "column": "AvgLatency", "label": "Avg Latency" , "format": ",.2f" },
        { "column": "AvgPacketLoss", "label": "Avg Pkt Loss" , "format": ",.2f" },
        { "column": "timestamp", "label": "Timestamp", "timeFormat": "%b %d, %y %X"}
    ]
},

[curran]

@ronakmshah This is implemented in PR #188. I did not see the same thing as your screenshot under dashboards/aarDomain, so I added formatting for another table instead - public/configurations/visualizations/top20-talkers-domain.json. You should be able to take for formatter configurations introduced in #188 and apply them where you need formatting in all tables.