[BUG] Too many digits on Request / Response Body Size

[NghiaTranUIT]

🐶 Brief

In the latest version, they request and response body size have many redundant digits.

👑 Criteria

• Should be round to 1 floating digit

[shirshak55]

haha this floating point digit is always pain in ass :) Specially in JS as it only has f64 it even gets more irritating.

[NghiaTranUIT]

In the past, I encountered this floating pain when parsing the number in JSON too (#169). It's weird that the JSONSerialization class in Foundation framework doesn't handle it properly and our developer have to fix it manually. 😅

[NghiaTranUIT]

All done 🎉

Changelogs

• Fix formatter.maximumFractionDigits in NSNumberFormatter

[shirshak55]

@NghiaTranUIT what will happen if the data was actually 70.000000001?

[NghiaTranUIT]

We round it up to 70 (Bytes) 😄

[shirshak55]

hmm i am that is problem right? Lets say I am working on money endpoint and supplied 70.00001 and proxyman made it 70 and i mock that response to test api server now it will fail because my api server consumer expects it to be 70.00001 not 70 . SO I think proxy man should serve same response given by server and should not roundup etc.

[NghiaTranUIT]

The size of the response remains as it is (70.00001) and your Test API server won't be failed. It only rounds up for the presenter on the flow panel.

If we need the precise value, I suppose that I would implement the Summary tab, which presents all essential data without round up.

[shirshak55]

i mean if i save response to disk will it modify according to presenter or it will save response as it should?