Price Precision Config

[enescakir]

Thanks for great tool.

Number of the digits after the decimal point isn't enough especially for cryptocurrencies. Currently, precision is set to 2 in ticker/internal/ui/util/format.go >> ConvertFloatToString(f float64) string file. It's very small. precision configuration might be great.

I thought to open a PR, but I couldn't find a way to access config value in ConvertFloatToString. I didn't want to add precision as parameter to lots of places such as ConvertFloatToString, ValueText, watchlist.NewModel, watchlist.item etc.

[achannarasappa]

I wonder if there is a sensible default that could be applied here.

If we were to expose an option to set precision globally, stocks with high and low value per unit may look odd e.g. (100000.00000 and 0.00013).

This issue warrants a solution but what the solution is is not yet clear to me.

[enescakir]

Maybe we can decide it for each stock automatically. Yahoo Finance shows max 4 digits min 2 digits after dot.
It might me something like that

       stock < 10       --->   precision: 4     i.e.: 0.4375, 1.5436
 10 <= stock < 100      --->   precision: 3     i.e.: 10.543
100 <= stock            --->   precision: 2     i.e.: 100.30, 49435.97

If it makes sense to you, I can open a PR for it. https://play.golang.org/p/KeT4xrw4p6n

[achannarasappa]

Your suggestion looks sensible to me. A PR would be very much welcome :)