Fix an issue with negative request/response sizes displayed.

[MiSikora]

📷 Screenshots

Show us what you've changed, we love images.

📄 Context

Why did you change something? Is there an issue to link here? Or an extarnal link?

I introduced a bug with one of the previous PRs.

📝 Changes

Which code did you change? How?

I modified the response/request length on the UI level to display at lest 0 as a minimum value.

⚠️ Breaking

Is there something breaking in the API? Any class or method signature changed?

No.

📝 How to test

Is there a special case to test your changes?

Run the sample app. Requests and responses should display 0 B instead of -1 B for some of the responses.

🔮 Next steps

Do we have to plan something else after the merge?

No.

[vbuberen]

Hi again @MiSikora.
It wasn't your bug that you see -1 - this value is returned when contentLength size is unknown (API returned nothing in this header).
You can see more info here: #209
Till the time we introduce our own mechanism of size calculation, I would leave -1, since 0 isn't technically correct.

[MiSikora]

Oh, ok. I agree it makes sense to show -1 in such cases. I thought I messed something up. I'll close this then. Thanks for the info.