toString instead of toLocaleString

[nguvictor]

This is workaround to get correct decimals to display, as the toLocaleString solution causes issues with number display
For example:

The problem is how Number and toLocaleString() loses precision. Example in dev console

[netlify]

✅ Deploy Preview for chipper-sunburst-578cfe ready!

Name	Link
🔨 Latest commit	0239f92
🔍 Latest deploy log	https://app.netlify.com/sites/chipper-sunburst-578cfe/deploys/65b130c90b75ff00085efba3
😎 Deploy Preview	https://deploy-preview-226--chipper-sunburst-578cfe.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[fliebenberg]

Havent looked at the front-end code for some time, but why don't we use the displayAmount function here. We know the decimals for the price is fixed, so just display it the same way you display prices in the actual orderbook buys and sells.

[EvgeniiaVak]

window.innerWidth
1295

the clash still happens, I guess we need to split it in two rows when the containing div is narrow

[Radstakes]

I think having the spread on a row below would be fine, or we could remove the spread value and just show the percentage?

[EvgeniiaVak]

I agree with using utils.displayNumber here, with something large for noDigits (so it wouldn't shorten the large prices with Ks and Ms, maybe 18?). I don't think we need to set upfixedDecimals param though, if we specify it, it will result in a lot of extra zeros for most pairs, which would not look pretty.

[EvgeniiaVak]

I think having the spread on a row below would be fine, or we could remove the spread value and just show the percentage?

even if we remove the spread value, if the price number is very long it might still overlap, moving spread to a row below (but only if they don't fit) would be better

[fliebenberg]

I agree with using utils.displayNumber here, with something large for noDigits (so it wouldn't shorten the large prices with Ks and Ms, maybe 18?). I don't think we need to set upfixedDecimals param though, if we specify it, it will result in a lot of extra zeros for most pairs, which would not look pretty.

I think using displayNumber with noDigits set to 10 should work fine. It is very unlikely that prices will ever be more than 9 999 999 999. The priceMaxDecimals for any price higher than 99 999 will be 0. The most decimals a price could ever have is 8, so even in that case a noDigits of 10 should work ("0." and 8 decimals = 10 digits).
I agree that only displaying % spread when space is low should be fine.